Konrad Windszus wrote > There is one paragraph which doesn't really make sense in that documentation: > > ... > The Sling Event Support adds the notion of a job. A job is a special event > that has to be processed exactly once. > To be precise, the processing guarantee is at most once. However, the time > window for a single job where exactly > once is very small and only happens if the instance which processes a job crashes after the job processing is > finished but before this state is persisted. Therefore a job consumer should be prepared to process a job more than once. > ... > > I don't get that paragraph and it seems there is something missing in the > sentence "However, the time window for a single job where exactly once is > very small and only happens if the instance which processes a job crashes > after the job processing is finished but before this state is persisted.". > > Even without the sentence I don't get the "at most/exactly once" guarantee, > because exactly in the case where a job has been finished but its state not > yet persisted would lead to execution of the job more than once. > Maybe one should outline as well the case when the job is never processed at > all. I assume this can only happen if there is no according JobConsumer being > registered. > > @Carsten: Can you clarify that paragraph a bit?
Yepp, there is really something missing in that sentence :) I'll try to clarify Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
