Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ObjectRemoved event may not be fired #110

Open
mcdonc opened this issue Aug 31, 2013 · 3 comments
Open

ObjectRemoved event may not be fired #110

mcdonc opened this issue Aug 31, 2013 · 3 comments
Milestone

Comments

@mcdonc
Copy link
Member

mcdonc commented Aug 31, 2013

If someone subscribes to an object removed event with a particular context but the object is removed indirectly (by perhaps deleting a folder in which it lives), the event will not be fired.

@tseaver
Copy link
Member

tseaver commented Aug 31, 2013

The cost of firing all those events is too high to make everyone pay. Applications which need this behavior should register a "re-broadcasting" subscriber, which converts the original event to a set of events, one each for the transitive closure of its items.

@mcdonc
Copy link
Member Author

mcdonc commented Sep 1, 2013

Agreed. It just needs to be documented well I think.

@mcdonc
Copy link
Member Author

mcdonc commented Sep 3, 2013

This is basically a documentation task that should explain that to catch all remove events, you'll have to register a subscriber for ObjectWillBeRemoved without any context (so it will be fired whenver any object is deleted) and resolve all oids in event.removed_oids.

@cguardia cguardia modified the milestone: Alpha 2 May 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants