> Hi, > > On 21/09/16 08:13, "Carsten Ziegeler" <cziege...@apache.org> wrote: > >> Finally, recently some people suggested that we support all of Oaks >> filtering possibilities for the ResourceChangeListener. I'm not a fan of >> that - first of all, we should only support what is really needed. >> Second, as soon as we support it, it means that every resource provider >> needs to support it which might but a high burden for nothing on the >> implementations. And finally, as we already see with the globbing, >> filtering is nice but we have to be careful for remove events and >> clearly specifiy how this works - and specify it in a way that it really >> works for the listeners. > > What about support for the famous ExcludeExternal? >
That's already there - a listener by default just listens for local events. If it implements ExternalRCL as well (marker interface), it gets the external events as well Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org