In a discussion [0] within the Oak mailinglist it became clear that the way Sling listens zu JCR Repository Changes and transforms all of them to events will not scale well in some big scale scenarios that oak is aiming to enable. Therefore the question was posted if it would be feasible and/or even necessary to refactor the API and deprecate (or at least discurrage) registration in a global scope as currently done.
Since I do not want to copy & paste parts of the discussion I do hope that the participants of the oak discussion add the remaining options with some more detail about consequences than can be found in the linked discussion. It would be great to also get some feedbacks of consumers of the existing API about the usage to identify how finegrained a potential registrationlogic with paths/properties might need to be. Best regards Dominik [0] http://markmail.org/message/n5vllhjoawypteck
