This sounds like a great idea. One thing I like about these services, particularly those based around REST over HTTP, is that they're simple to use, intuitive and easily integratable, no special client libs required.
Are there any common/standard APIs/protocols that do this? Would this look similar to something like Amazon SQS? On 9 Nov 2016 17:55, "John D. Ament" <john.d.am...@gmail.com> wrote: > All, > > One thing I see come up quite often when looking at cloud based messaging > systems is the concept of a reservation (there's a couple of terms out > there, reservation seems to describe it best). The reservation acts like > this: > > - Client polls for messages and get some number of messages back. > - When a client polls again, those messages are not returned for some > duration since it read them. > - The messages are not auto-acknowledged. > - A second API is invoked indicating that the client has acknowledged that > message, typically using some message id or reservation id. > - If after some duration, a message was not acknowledged, it becomes > eligible for reception again. > > I'd like to add this type of capability to the REST API for Artemis. What > do others think? > > John >
