Jim Fulton wrote at 2005-8-23 14:22 -0400: > ... >>>For example, you could have gotten to the same end here >>>with the old method, by registering your actions with an object of your own >>>creation, and registering just one commit hook with the transaction, where >>>that one hook looked at the actions you registered with your own object and >>>ran them in whatever order _it_ determined was best. >> >> >> Now plug and play comes into play: >> >> Assume two packages developped by independent people >> which all want to control the order of hook execution. > >Do we have evidence that such applications exist? So far, the >only example I've seen is one where an application wanted a handler >to go last. As I've pointed out in a separate note, this is achievable >without the change.
I have a *package* (similar to Archetypes SQLStorage) that wants to go after everything that might possibly change attributes whether those changes are done by another component from me or any package developped by someone else. -- Dieter _______________________________________________ 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