[Shane Hathaway]
| It means that a correctly operating ZODB will behave this way.
Oh, I see. Thanks for clarifying that. :)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encodi
> > | >
> > | > I just want to check if things work the way I think (hope) it does.
> > | >
> > | > In a transaction, are objects attributes safe from other threads.
> > | >
> > | > self._v_mytemp in my request does not conflict with other requests?
> > |
> > | This is correct (or it's supposed to
Erik Enge wrote:
>
> [Shane Hathaway]
>
> | Johan Carlsson wrote:
> | >
> | > I just want to check if things work the way I think (hope) it does.
> | >
> | > In a transaction, are objects attributes safe from other threads.
> | >
> | > self._v_mytemp in my request does not conflict with other re
[Shane Hathaway]
| Johan Carlsson wrote:
| >
| > I just want to check if things work the way I think (hope) it does.
| >
| > In a transaction, are objects attributes safe from other threads.
| >
| > self._v_mytemp in my request does not conflict with other requests?
|
| This is correct (or it
Using a mutex by way of example, without using anything Zope-specific
(the following uses the Python threading module):
import threading
lock = threading.Lock()
myglobal = []
def changeglobal(val):
lock.acquire()
try:
myglobal.append(val)
finally:
lock.release()
> >
Johan Carlsson wrote:
>
> I just want to check if things work the way I think (hope) it does.
>
> In a transaction, are objects attributes safe from other threads.
>
> self._v_mytemp in my request does not conflict with other requests?
This is correct (or it's supposed to be.) Each thread has
