"Kevin Dangoor" <kid@kendermedia.com> wrote:
----- Original Message ----- From: "julio dinis" <juliodinis@hotmail.com> To: <zope@zope.org> Sent: Monday, February 07, 2000 5:02 PM Subject: [Zope] ZCatalog, catalogAware Zclass and Versions
This specific class creates me a Site Operation/Development problem every time I start a version. This is because if in my version I create some objects of my Class they would be indexed (again my genial brain!), then locking my catalog, i.e, the methods I have for people to create objects will no longer work because my version is locking the catalog.
If there is a way/how-to to a version dont do this I would apreciate feedback. Meanwhile... if I discover a good method I'll post on the list.
I don't believe there is a way. Earlier, I think Michel may have mentioned having some ideas on having less aggressive locking... but, that seemed to be a somewhat distant future feature.
I think from discussions with Chris Petrilli at IPC8 that DC has a solution to this one on the "near term" track (it is a show-stopper for many uses of Versions). The core of the idea is to reify the individual nodes within the Catalog, so that a change to a CatalogAware object within a Version locks only that node, rather than the whole catalog. -- ========================================================= Tres Seaver tseaver@palladion.com 713-523-6582 Palladion Software http://www.palladion.com