durusmail: quixote-users: Re: Organizing a Quixote/Durus multiprocess application
Organizing a Quixote/Durus multiprocess application
2006-08-28
Re: Organizing a Quixote/Durus multiprocess application
2006-08-28
2006-08-28
2006-08-29
Organizing a Quixote/Durus multiprocess application
2006-08-28
2006-08-29
2006-08-29
2006-08-29
2006-08-29
2006-08-30
2006-08-31
Mike Orr (2 parts)
2006-09-01
Organizing a Quixote/Durus multiprocess application
2006-08-29
Re: Organizing a Quixote/Durus multiprocess application
Mike Orr
2006-08-28
Oh look, another issue.  Where do I set my Durus ClientConnection in a
SCGI app with multiple processes?  Do I have to open a
ClientConnection for every request (ugly)?  Apparently sockets can't
be inherited by child processes, or at least that didn't work with
MySQL ("bad file descriptor").  I could override
scgi.scgi_server.SCGIServer.spawn_child() and set the connections
there, but that seems kludgey.  Do .spawn_child and .reap_children
need a hook method for per-process initialization?

I'm wondering if this will affect session2.store.DurusSessionStore
too.  It currently accepts a live db connection in the constructor,
but that is called before the children are created.  (I set up the
session and then pass it to the Publisher factory.)

--
Mike Orr 
reply