My plan for getting autoreload to work as an NT service was to split the service into 2 processes -- a "controller" that plays the role of AppServer.bat, and the actual app server as a child process. The service process would fire off a child process to run the appserver, then wait for it to exit, and start it up again if the exit code was 3.
Does this sound reasonable? - Geoff > -----Original Message----- > From: Luke Opperman [mailto:luke@;metathusalan.com] > Sent: Thursday, October 31, 2002 8:24 PM > To: Webware discuss > Subject: Re: [Webware-discuss] Deprecating OneShot.cgi > > > I'll only add, we still use OneShot.cgi EXTENSIVELY on our > development server, > and will continue to do so for the near future, as our main > dev server is win2K > running as a service. > > But I absolutely vote for deprecating it, as it really feels > like a hack, and > has lead to late-found bugs due to the differences. We'll > continue to use it > secretly, probably put some time towards getting AutoReload > to work as a > service, and be happy. > > Remove it from the docs! Yay! > > - Luke > > > > ------------------------------------------------------- > This sf.net email is sponsored by: Influence the future > of Java(TM) technology. Join the Java Community > Process(SM) (JCP(SM)) program now. > http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en > _______________________________________________ > Webware-discuss mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/webware-discuss > ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
