--On 2. Juli 2008 16:45:53 -0400 Joseph Turian <[EMAIL PROTECTED]> wrote:
How do I "lock" zodb objects?
Zope provides locking for WebDAV under the hood. Means you can not
lock/unlock objects directly through the Zope UI (except the global webdav
lock manager in the ZMI for _unlocking_ cont
On Wed, Jul 02, 2008 at 08:07:56AM -0400, Erik Dahl wrote:
> I have a situation where I want to mutate the class of an instance like
> this:
>
> inst.__class__ = NewClass
Is inst a persistent object? Then your only chance to get this to work
is to find *all* objects that reference inst and mark
How do I "lock" zodb objects?
I want the following process:
See if key is present in root.
[it's not]
Lock key write-access, so that no other client will try to write key.
Compute value for key.
Write value for key.
Unlock key.
How do I achieve this?
Thanks!
Joseph
--
Academic: http://www-e
Erik Dahl wrote:
I have a situation where I want to mutate the class of an instance
like this:
inst.__class__ = NewClass
I'm in zeo land. When I do this in one client things work fine. But
of course the other clients who have already loaded the instance still
hold the old class. Restar
--On 2. Juli 2008 08:07:56 -0400 Erik Dahl <[EMAIL PROTECTED]> wrote:
I have a situation where I want to mutate the class of an instance like
this:
inst.__class__ = NewClass
I'm in zeo land. When I do this in one client things work fine. But of
course the other clients who have already loa
> Any chance I can get zeo to tell the other clients about the new class?
Speaking purely as an idiot .. can't you tell ZEO the normal way? I.e.
just make it think the instance changed. Edit it, or set _p_changed on
it.
--
jean . .. //\\\oo///\\
_
I have a situation where I want to mutate the class of an instance
like this:
inst.__class__ = NewClass
I'm in zeo land. When I do this in one client things work fine. But
of course the other clients who have already loaded the instance still
hold the old class. Restarting them gets the
