Quote: I thought running Sesaem as a service would be more secure since you dont have to "log in" to windows. (Just a guess).
Yes. You would not have to leave a system logged in if you ran Sesame server as a Win32 service. Nor would you have to log in to start the server. So in both those cases there is an advantage.
You must be careful to make sure that the services on which Sesame relies are already running before Sesame starts as service. Dependency checking for services in WIn32 is done using registry enties. They are not set up by default. In the case of Sesame, TCP/IP services must be up and running before Sesame is started.
Additionally, it is critically important that Sesame server be properly shutdown before the service representing it is stopped. Win32 OSs simply kill the process (using "TerminateProcess") giving it no notification or warning. That will cause the server to drop suddenly, even if it is mid-operation.
Worse, because of "limitations" in WinNT, a service can either have "interaction with the desktop" or "interact with the network" but not both. Sesame in normal mode, does both. Using "-daemon" flag may help with this, but I can't be sure.
On top of all of that, Win32 sends services messages that are not processed by normal tasks when the user logs off. The default method invoked for this message is to suddenly terminate the process. Sesame does not directly handle any Windows messages, and I would hate to add non-portable code to handle this unique windows-ism.
As far as security goes, Sesame is based on TCP/IP - a well known and well documented (older than DOS or Q&A) standard, on which security layers can be added through standard and documented means. I don't know if Win32 "services", being completely proprietary, respect and adapt to TCP/IP security measures. I can't even say for sure if Win32 OSs aren't stopping and restarting the processes they represent in somewhat arbitrary ways.