If you specify "threaded =3D True" in the constructor of the session
pool, Oracle guarantees thread safety provided you use one thread for
each connection you use. If you want more than one thread to access a
connection, you will have to synchronize access. Does that explain the
matter sufficiently?
On 9/12/05, Forest Wilkinson <mo...@ti...> wrote:
> I'm using cx_Oracle SessionPool objects in a threaded http server. Since
> I didn't see an explicit statement in the docs that SessionPool.acquire()
> and SessionPool.release() are thread safe, I'm currently synchronizing
> access to those methods with a threading.Condition object. Is this
> necessary? If SessionPool does its own method synchronization, I'll get
> rid of my wrapper class and perhaps get better performance.
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practic=
es
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q=
A
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> cx-oracle-users mailing list
> cx-...@li...
> https://lists.sourceforge.net/lists/listinfo/cx-oracle-users
>
|
