> As far as deployment is concerned, you logon as > administrator, install the service, then logoff. The service > then no longer needs to be running in anyone's logon and it > will magically fire back up whenever the system is rebooted. > Ya, you have to force an account that it will logon to when > it starts up. It's a service. This is how they work in > windows land. If microsoft can get the bloated pig monster > that is IIS running as a service then I think something like > jabberd should be pretty straight forward. The jabber server > should run as a service under windows. Period.
>From what I remember, Windows services require the app/service to implement a special API. So unless JabberD's windows build does this, it will either require the additional code, or a wrapper program. > >From the development standpoint: Since the server is is pretty much a > console application turning it into a bona fide service > should be a cakewalk. > > How all this fits into the cygwin library, however, is a > mystery that I will probably be messing around with shorty. Cygwin probably provides a nice path, but certainly not the only approach. Thanks, Mike _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
