From: David Binger [mailto:binger@centre.edu]
What prevents id collisions in Zope? It looks like the the ObjectManager.py code checks to see if the id is taken, and then it reserves the id. Is there a danger that 2 processes/threads (z2.py -t 4?) could both check and reserve the same id? Is there something in Zope that prevents this (improbable, but perhaps possible) problem?
Is there certain way to find an object id that is not taken?
The ZODB takes care of concurrency and conflicts. I fyou want to know the technical details, see the UML model of the ZODB: http://www.zope.org/Documentation/Developer/Models/ZODB/ -- Martijn Pieters, Software Engineer | Digital Creations http://www.digicool.com | Creators of Zope http://www.zope.org | mailto:mj@digicool.com ICQ: 4532236 | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 -------------------------------------------