-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Julien Anguenot wrote:
I'm gonna respond to a number of emails at once. :)
Tim Peters wrote:
[Tim]
...
Julien provided links to code that already uses the new feature:
As an Indexation Manager :
Jim Fulton wrote at 2005-8-24 16:08 -0400:
...
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.
So again, you
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
On 8/22/05, Tim Peters [EMAIL PROTECTED] wrote:
Jim still wonders, and he got me wondering too, whether the `order=` gimmick
is really needed. 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
[Tim]
...
Julien provided links to code that already uses the new feature:
As an Indexation Manager :
http://svn.nuxeo.org/trac/pub/file/CPSCore/trunk/IndexationManager.py
As an Event Manager :
http://svn.nuxeo.org/trac/pub/file/CPSSubscriptions/trunk/EventManager.py
He appears to use
Tim Peters wrote:
[Tim]
...
Julien provided links to code that already uses the new feature:
As an Indexation Manager :
http://svn.nuxeo.org/trac/pub/file/CPSCore/trunk/IndexationManager.py
As an Event Manager :
http://svn.nuxeo.org/trac/pub/file/CPSSubscriptions/trunk/EventManager.py
He
[Jim Fulton, on Julien's addBeforeCommitHook() change]
What is the motivation for this? Can you give any use cases?
I'm -1 on this because it adds complexity to something that I think
should be simple. It feels like something that is likely to be missused.
I do have an open mind though.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Julien Anguenot wrote:
[...]
I would like to order the before commit hooks on a transaction by being
able to specify an order for a subscriber at registration time. For the
moment, they are called in the order they've been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Peters wrote:
[Julien Anguenot]
...
To make it clear the idea is if you got this and if we call it order.
Callback Ca order 0
Callback Cb order 99
Callback Cc order -99
The order of execution will be Cc Ca and then Cb.
Note the ones
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I created a branch there :
http://svn.zope.org/ZODB/branches/anguenot-ordering-beforecommitsubscribers/
See changeset 37789
Check the changeset log for more information about the implementation.
J.
Julien Anguenot wrote:
Hi,
I
On Aug 5, 2005, at 6:20 AM, Julien Anguenot wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I would like to order the before commit hooks on a transaction by
being
able to specify an order for a subscriber at registration time. For
the
moment, they are called in the order
On Aug 5, 2005, at 2:33 PM, Tim Peters wrote:
[Julien Anguenot]
...
The order argument could be an integer with a default value to 0
added
to the registration method.
[Gary Poster]
I usually like the word 'priority' for this sort of value, rather
than
'order'. To me 'order' implies
12 matches
Mail list logo
