AW: [smila-dev] RE: FYI :: new feature :: Message Resequencer

[<Daniel.Stucky@xxxxxxxxxxx>]

Hi Igor,

I fully understand what you propose, but it just doesn't work when you have multiple Queues and so multiple processing pipelines. As you would remove the lock just after the first pipeline has finished, but the lock must only be removed if the full workflow (all pipelines are completed or processing is stopped because of some error.

Bye,
Daniel

-----Ursprüngliche Nachricht-----
Von: smila-dev-bounces@xxxxxxxxxxx [mailto:smila-dev-bounces@xxxxxxxxxxx] Im Auftrag von Igor.Novakovic@xxxxxxxxxxx
Gesendet: Donnerstag, 8. Oktober 2009 11:25
An: smila-dev@xxxxxxxxxxx
Betreff: AW: [smila-dev] RE: FYI :: new feature :: Message Resequencer

Hi,

> yes, I agree that we would need some kind of Record locking. 
Ok.

> But this cannot be
> done in a Listener, as you may have a setup with multiple Queues,
using multiple
> Routers/Listeners. 
When the Connectivity tries to store the record for the first time then
the blackboard should lock it. The router can then enqueue the message
in some queue.
When Connectivity now tries to store another version of the same record
the blackboard should read the "lock" and deny its update.

> What we need is some kind of mechanism that reports to
> Connectivity that processing of a Record finished (either successfully
or with an
> error). 
The listener consumes the message from the queue and when the processing
is done it should not remove the message from the queue but also remove
the lock (by calling blackboard).

Regards
Igor
_______________________________________________
smila-dev mailing list
smila-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/smila-dev