Re: [ZODB-Dev] Locking

2008-07-03 Thread Marius Gedminas
On Wed, Jul 02, 2008 at 04:45:53PM -0400, Joseph Turian wrote:
 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.

Usually you shouldn't need to do this.  ZODB will detect conflicting
write transactions and raise ConflictError that you're supposed to catch
and retry up to a certain reasonable number of times (3 or 5).

Marius Gedminas
-- 
Key emulation:
[ ] Intuitive
[*] Emacs(Seen in an MCEdit dialog) 


signature.asc
Description: Digital signature
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zodb-dev


Re: [ZODB-Dev] Locking

2008-07-02 Thread Andreas Jung



--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_ content).





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.



Look at Plone utilizing the webdav locks for app-level locking support.
Or: you can the API in Zope for using the webdav locks (somewhere in the 
'webdav' module, check yourself).


-aj

pgpFtOFSS4kG8.pgp
Description: PGP signature
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zodb-dev