Today the contained events interfaces are:
From the archives I can find this was decided after:
but without motivation for this part. I'm still looking for the
Before that proposal, the hierarchy was:
class IObjectMovedEvent(IObjectAddedEvent, IObjectRemovedEvent)
I contend that this second hierarchy is much more useful to deal
with. The arguments I have are in the use cases explained in:
where you can see the hoops one has to go through to react to objects
being created, deleted or moved with the current event hierarchy.
I'd like to know what non-framework use cases people have today with
the current event interfaces hierarchy, and if they really find it
more useful than the old one.
If not, or if the use cases are borderline, I'd like to propose that
the hierarchy be moved back to the second form. This would have to go
through a deprecation phase, I'm not sure exactly how, but if there's
consensus we can find a way.
Myself I consider the current hierarchy to be a design bug.
Florent Guillaume, Nuxeo (Paris, France) Director of R&D
+33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED]
Zope3-dev mailing list