I haven't run into this scenario yet with Quixote, but I'm anticipating it
based on prior experience with other web publishing techniques.

Does anyone have any Quixote specific tips/experiences that could be helpful
in handling long running requests in Quixote?  I'm talking about requests
that for some reason or another (perhaps a long-running DB query) take a
long time to get handled (maybe 30 seconds or so).  My thoughts are that if
you're running a dedicated server like Medusa, it's gonna have to be
multi-threaded, and if you're using CGI, it's a non-issue (multi-process),
but the overall performance is terrible, etc...

Utimately, I figure you've got to throw processes or threads at it to keep
the application usable for the other users when a single process (or thread)
gets tied up by a long request, but I'd like to hear people's experiences in
this regard.  I know that part of Quixote's recent re-factoring should make
making it multi-threaded easier, and that there's a brief kick-start on the
subject in the docs, but I'm not sure that's the way to go, as it gives rise
to the issue of making sure the app (running under Quixote) is also
thread-safe...

I guess I lean toward throwing processes at it, but I'd really like to hear
the thoughts of those with more Quixote experience than I have.

Thanks,

Jason Sibre