Posted by Brian Levantine on March 17, 2007 at 12:54:03:
In Reply to: Re: COMET-as-Service -- At reboot --> two part question posted by Jon Sacks on March 16, 2007 at 07:39:28:
CometAsService uses CometAsService.ini to initialize the Comet application. The CommandLine parameter is more or less the same as a desktop shortcut except there is the additional /SERVICE parameter. As I stated earlier, If you start COSC instead of Comet.exe, You'll get Comet started but without a session 0 console. As soon as you execute COSW from a local user session, it will connect to the running COSC as session 0. But keep in mide what I said earlier about not using Comet.exe (you'll loses the auto-update feature).
As for your problem with the handling of a downed server, that is not so easily fixed. Basically, you'll need to stop and restart CometAsService so that it can re-establish the connections.