I'm a bit puzzled - can you explain a bit why you think it's a bad idea ???
I hope you realize this is not 'prefork' mode ( i.e. forking a tomcat on each request ), just wait for the first connection and pass the server socket descriptor. It's by far the cleanest method to run tomcat on port 80 - either via xinetd/launchd, or via another native wrapper ( compare it with commons-daemon ). And the only clean method I know of loading tomcat on demand - instead of keeping it running and taking memory all the time. Tomcat is not used only for big servers, but also for development and smaller servers - I don't like my memory used by code that I run only once in a while. Costin On 11/24/05, Bill Barker <[EMAIL PROTECTED]> wrote: > > <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > Author: costin > > Date: Wed Nov 23 21:34:19 2005 > > New Revision: 348665 > > > > URL: http://svn.apache.org/viewcvs?rev=348665&view=rev > > Log: > > Another experiment - this class uses NIO to get the socket from Xinetd ( > > I'll also try > > with launchd ). This allows starting tomcat on-demand, from xinetd/lauchd. > > Work in progress, I also want to shutdown when idle for too long. > > > > This is also targeted to embeded/desktop use. > > > > About the most useless waste of svn space I could imagine. I mean, it's > like a total reason to close off the sandbox right here. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
