On Fri, 2002-11-01 at 11:49, Nick Murtagh wrote: > This looks like a handy feature, but I have a couple of questions: > > Can you use this in production, or will there be a period where no > requests can be handled while the AppServer restarts?
I'm not sure if you should use it during production, but the AppServer can restart quickly enough that no requests will be dropped (the adapters all retry connecting to the AppServer, and the timeout for those retries is longer than the AppServer takes to restart). > Why restart the AppServer? Wouldn't it be possible to reload > modules when they have changed, or is this a massive can > of worms that shouldn't be opened? Yes, it's a big can of worms :) Basically if you change a class there'll be a large number of stale objects lying around, even if you reload the module. Ian ------------------------------------------------------- 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
