On 21/09/16 14:28, "Carsten Ziegeler" <cziege...@apache.org> wrote:
>> On 21/09/16 14:14, "Robert Munteanu" <romb...@apache.org> wrote: >> >>> On Wed, 2016-09-21 at 14:11 +0200, Stefan Egli wrote: >>>> On 21/09/16 11:26, "Robert Munteanu" <romb...@apache.org> wrote: >>>> >>>>> >>>>> On Wed, 2016-09-21 at 11:18 +0200, Carsten Ziegeler wrote: >>>>>> >>>>>> So we a) need to clarify the contract and b) think about what we >>>>>> do >>>>>> if >>>>>> someone registers for a glob pattern. Do we send removal of >>>>>> parents >>>>>> automatically or do we expect to listener to register at /? >>>>> >>>>> I would say that we send removal of parents automatically, it's >>>>> simpler >>>>> for the clients. >>>> >>>> Ok, I start to see the advantage of getting automatically notified on >>>> parent removal.. am thinking though if such a choice should not be up >>>> to >>>> the listener (perhaps yes, with default 'true')? >>> >>> In what scenarios would it be useful to have this choice? >> >> Good question, I'll try to come up with one :) Not in the cache >>scenario, >> agreed. How's the exact definition here though: say you register for >> removal of **.jsp - are you getting notified *only* for parents that >> actually contain any *.jsp I assume? Otherwise I'm expecting noise.. >> >How does the sender now? Depending on how you implement the observer in oak it could be done. But exactly, it's potentially expensive as it has to do a traversal of a removed subtree. Cheers, Stefan
