Hi Am 22.10.2013 um 15:52 schrieb Jukka Zitting:
> Hi, > > On Tue, Oct 22, 2013 at 9:41 AM, Felix Meschberger <fmesc...@adobe.com> wrote: >> The JcrResourceListener just gets JCR Observation events, creates the OSGi >> Event objects >> and hands them over for distribution by the OSGi EventAdmin service. The >> latter service is >> then responsible for dispatching taking the EventHandler service >> registration properties into >> account for filtering. > > Right, but the problem here is that this design can't scale out to > millions of events per second, as it requires each individual OSGi > Event to be instantiated before filtering. The proposed service > interface doesn't need to do that, so it can achieve a much higher > throughput, and since no event queue is needed, there's no need to > worry about the queue filling up. That's one Event object per event -- not one event per listener per event. This is completely different to JCR. Regards Felix > > BR, > > Jukka Zitting
smime.p7s
Description: S/MIME cryptographic signature
