Jeremy Hylton wrote:
> It's really too bad that ZEO only allows a single outstanding request.
>  Restructuring the protocol to allow multiple simulatenous requests
> was on the task list years ago, but the protocol implementation is so
> complex I doubt it will get done :-(.  I can't help but think building
> on top of an existing message/RPC layer would be profitable.  (What's
> twisted's RPC layer?)  Or at least something less difficult to use
> than asyncore.

Do you think the RPC layer is the source of the problem?  I feel like
the way ZODB uses references in pickles is the main thing that slows it
down.  Even if you have a protocol that can request many objects at
once, the unpickling machinery only asks for one at a time.

For more information about ZODB, see the ZODB Wiki:

ZODB-Dev mailing list  -

Reply via email to