Laurence Rowe wrote:
I'm not sure connection pooling is really useful in a threaded
environment with recycled sessions. You want n threads = n connections.
If we started creating new sessions each request then things would be
Mike Bayer says the following:
> you should reuse a single engine. It contains a pool of connections,
> so recreating engines means new connections are constantly rebuilt and
> it defeats the purpose of the pool. Other than that the creation of
> an engine is not very expensive but even a small expense is needless
I explained to him we'd only end up creating a single engine per thread
(and app), and we'll see what he has to say about that.
I'm leaning towards trying to recycle the engines, though.
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -