John D. Heintz writes:
I am using ZODB along with CORBA to expose peristent objects. Some of
my objects have per-connection/session state.
...
My initial idea is to have a _v_position attribute ...
Using "_v_" attributes for session state is a very bad idea.
They are thread(!) local and
Thanks for the warning Dieter,
but I'm managing threads/connections/sessions/POAs and a few other
things already to expose ZODB objects through CORBA sessions.
I wanted the _v_* attributes to live for the life of the DB Connections.
Last night I found a fix for the bug that prevented me from
Hello all,
I am using ZODB along with CORBA to expose peristent objects. Some of
my objects have per-connection/session state. The clear example is
file-like objects - effectively exposing persistent StringIO objects
through CORBA.
The issue is that I want multiple clients to be able to
