02-02-2024, 04:48 AM
There is a small performance difference. The service is faster because it doesn't handle Windows messages, don't need to update the labels with bytes sent, request count, etc. Other than that, the HTTP(S) server is exactly the same so it will perform the same when responding to a request.
However, I'd just point out one particular case: Sometimes users create their own Stand Alone server (with a different main form). Depending on what you do in that main form, it can make the server unstable. For instance, you change or read global data without caring about concurrent access, or more specifically you are changing non-thread safe data in a non-thread safe way which is dangerous. I'd avoid some fancy SA servers with lots of bells and whistles (e.g. a grid with real time session list) unless you know exactly what you are doing.
PS: The grid with a real time session list is a true occurrence and, although it was actually a (thread) safe code, it was connected to a timer that was in charge of refreshing the session list each few seconds. A real performance penalty with very little utility other than "look what I did!" effect.
However, I'd just point out one particular case: Sometimes users create their own Stand Alone server (with a different main form). Depending on what you do in that main form, it can make the server unstable. For instance, you change or read global data without caring about concurrent access, or more specifically you are changing non-thread safe data in a non-thread safe way which is dangerous. I'd avoid some fancy SA servers with lots of bells and whistles (e.g. a grid with real time session list) unless you know exactly what you are doing.
PS: The grid with a real time session list is a true occurrence and, although it was actually a (thread) safe code, it was connected to a timer that was in charge of refreshing the session list each few seconds. A real performance penalty with very little utility other than "look what I did!" effect.