[ZODB-Dev] ZODB4 project plan

[Greg Ward]

[Jeremy, to me]
> I'm not sure why you say that every
> application outgrows the one thread, one transaction policy.  I have
> found it works exceedinly well for many applications.

OK, not *every* application.  I over-stated the case.  But the
one-thread-one-transaction policy is arbitrary and it's just that -- a
*policy*.  As a general purpose-library, ZODB should provide mechanism,
not policy, whenever possible.

[Christian channels me]
> Well, in our case, Shane's suggestion is a godsend, because we *don't*
> want multiple threads at all. Perhaps Greg implied that many
> applications want separate transactions running at the same time without
> having separate threads (apps using mainloop and coroutines come to
> mind)

Yes, exactly.

     Greg
-- 
Greg Ward - software developer                gward@mems-exchange.org
MEMS Exchange                            http://www.mems-exchange.org