Re: Observation: External vs local - Load distribution

[Carsten Ziegeler <cz...@apache.org>]

Am 17.06.15 um 10:35 schrieb Carsten Ziegeler:
> Ok, just to recap. In Sling we can implement the Observer interface (and
> not use the BackgroundObserver base class). This will give us reliably
> user id for all local events.
> 
> Does anyone see a problem with this approach?
> 
Getting back to this problem, it seems the above does not work, as the
DocumentNodeStore is not passing on the commit info to the observer in
the case of external events.
So no matter how I implement my observer, I don't get the info passed in.

Can someone please confirm this?

Thanks
Carsten
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org

Re: Observation: External vs local - Load distribution

[Stefan Egli <st...@apache.org>]

Hi Carsten,

For external events the commit info is indeed not provided yup.
For internal ones it is - except for those 'overflow' ones which collapse
into a pseudo-external one.

Cheers,
Stefan

On 13/10/15 15:17, "Carsten Ziegeler" <cz...@apache.org> wrote:

>Am 17.06.15 um 10:35 schrieb Carsten Ziegeler:
>> Ok, just to recap. In Sling we can implement the Observer interface (and
>> not use the BackgroundObserver base class). This will give us reliably
>> user id for all local events.
>> 
>> Does anyone see a problem with this approach?
>> 
>Getting back to this problem, it seems the above does not work, as the
>DocumentNodeStore is not passing on the commit info to the observer in
>the case of external events.
>So no matter how I implement my observer, I don't get the info passed in.
>
>Can someone please confirm this?
>
>Thanks
>Carsten
>-- 
>Carsten Ziegeler
>Adobe Research Switzerland
>cziegeler@apache.org