jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcel Reutegger <mreut...@adobe.com>
Subject RE: ObservationDispatcher - dispatch queued events in separate threads
Date Mon, 22 Oct 2012 11:43:54 GMT
Hi,

this would change existing behavior and may break application code
when there are dependencies between listeners and how/when
they receive events.

I'm also not sure if your proposed change is in line with the spec.

Regards
 Marcel 

> -----Original Message-----
> From: Miroslav Smiljanic [mailto:smmiroslav@gmail.com]
> Sent: Freitag, 12. Oktober 2012 13:57
> To: dev@jackrabbit.apache.org
> Subject: ObservationDispatcher - dispatch queued events in separate
> threads
> 
> Hi all,
> 
> I was wondering what would be argument not to distribute queued events in
> "ObservationManager"  in separate threads.
> I mean after reading queued action, use thread from pool to serve
> EventConsumer.consumeEvents(action.getEventStates());
> 
> I saw the case where one of the listeners was taking to much time to finis his
> operation letting all other to wait.
> 
> Can someone give me light here? Thanks.
> 
> --
> Best regards,
> Miroslav


Mime
View raw message