[Web-SIG] Web Site Process Bus

Robert Brewer fumanchu at amor.org
Mon Jun 25 23:41:51 CEST 2007

Phillip J. Eby wrote:
> Meanwhile, if you get a start call, you must be starting, right?  So 
> why worry about the state?  It'd be simpler to just use 
> "before/during/after" messages the way Twisted does.  Your "block" 
> example could be replaced by waiting for the "after" message of the 
> desired state, for example.

I just realized I haven't really explained what "start" and "stop" mean.
I think you might expect it to mean "beginning of process" and "exit the
process". But instead, I'm envisioning a FSM that has an "idle" state
in-between process init/exit and "server" start/stop, so that, without
restarting the process, you can stop and restart (un/bind the socket,
etc) the server components. This should also facilitate a daemon parent
process having a single site Bus and starting/stopping child processes
that contain the WSGI app and server components, if that's the way you
want to compose your site.

Robert Brewer
System Architect
Amor Ministries
fumanchu at amor.org

More information about the Web-SIG mailing list