Hi

is the mems exchange quixote app structured such that it uses

apache --> cgi --> quixote --> zeo --> zodb

ie it does a cgi request on every web interaction, similar to how
the demo.cgi is setup in quixote.

I'm presuming it uses the zeo for concurrency issues?

Is there any reason the app doesnt have it's own server process permanently
running?


I'm currently writing an app(mainly xmlrpc and a few admin webpages),
in which I have quixote running inside twisted (hence no CGI) and
using the zeo/zodb but obviously there is more than one way to
structure to such a beast.
Having done this I'm just wondering about other scenarios' pro's and cons.

thanks

Jon