Hi,
> Is there a reason that you think the implementation under SLING-5646 won't > support the batch use case ? > > > One aspect that may differentiate asset processing from general job use case is the guarantees offered from the job delivery. Some use case would be fine with "at-least-one" or "maybe" delivery whereas some use case will need "exactly-one" delivery. Ideally, each use case could select the level of guarantee it needs depending on the use case. @Ian the MoM API at SLING-5646 and its existing activemq impl at does not seems to define clearly the delivery. Does that mean the jobs are meant to be delivered with "maybe" guarantees (and have the application layer handle the ack+re-send) ? Regards, Timothee
