Dieter Maurer wrote:
They're not redundant if you have a policy that means different departments use different subtrees of aZODB,
Maybe, they should comminicate how to use resources in their common Zope efficiently...
Maybe you should stop making facetious comments ;-)
and they each connect to different databases on different database servers.
You cannot pool connections when they go to different databases or servers.
true enough.
Zope's current method is a cheap attempt at connection pooling without doing real connection pooling,
It is reusing the existing ZODB connection pool. Reusing rather than reinventing is not so bad ;-)
...except when the pools have very differing requirements.
and one that uses _v_ variables in a very dodgy fashion...
The only problem with "_v_" variables is that they can disappear at subtransaction boundaries.
Yep, and with no attempt to close the RDB connection they represent, leaking DB connections... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk