I might also suggest moving the 'shutDown' function from ThreadedAppServer
into AppServer, since it wants the AppServer instance (retrieved from
AppServer) and calls the AppServer.initiateShutdown() method which is
defined within AppServer.
I am not clear on where the signal handling should be defined, but suspect
they could remain within ThreadedAppServer, and in fact we may want to
retain a reference in ThreadedAppServer for shutDown, but this could be done
through: "from AppServer import shutDown"
> -----Original Message-----
> From: Chuck Esterbrook [mailto:ChuckEsterbrook@...]
> Sent: Monday, December 16, 2002 4:52 PM
> To: webware-devel@...
> Subject: Re: [Webware-devel] Accessing the app server instance from
> On Monday 16 December 2002 04:38 pm, Stuart Donaldson wrote:
> > Couldn't this be done by AppServer.__init__()?
> > Then require that all AppServer's must initialize the base class
> > AppServer which they likely do anyway.
> Er, good point. :-)
> I need more sugar...
> > Is there any reason to have multiple AppServer's running? Would it
> > make sense that WebKit.globalServer be a function that returns the
> > server? Then if for any reason we end up with a more complex server
> > referencing system accesses would at least be going through a
> > function which could be modified to do the right thing.
> I can't imagine that there will ever be more than one AppServer in a
> single process. I'm willing to work off that assumption.
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility
> Learn to use your power at OSDN's High Performance Computing Channel
> Webware-devel mailing list