[Zope] - Httpdapy and Zope problems

[Paul Everitt]

Andreas wrote:
> > 1. Because Apache runs multiple processes, BoboPOS 
> databases will end up
> That's why all publisher serialize it to ONE LRP.

Currently.  That situation shouldn't last more than two months.

Honestly, many of the pieces have already shown progress:

1) BoboPOS3a1 was released.

2) We lined up Medusa, which is meant to form the core of our
concurrency architecture.  I know your answer is that Medusa isn't good
for long-lived transactions, but if you have a pool of handlers matched
to the thread pool in the application, people at least have the option
of stating the number of concurrent operations.

3) Jeff has already made progress on concurrent PCGI and you have shown
another fascinating technique for integrating with Apache.

4) Jim has had BoboPOS working atop SOLID for several months now.

5) We *finally* made the move to Python 1.5.

Once we get the source release out of the way, Jim can get back to tying
all these things together.  January ought to be a good month for
concurrency.

> Not really. I've been using a pcgi published app with MANY 
> threads and it
> works quite well :)

Presumably on Linux, right?  Want to share the details of your kernel
versions, etc. and any lessons you learned along the way?

--Paul