[jira] [Resolved] (ARTEMIS-847) Reservations via REST API

["Justin Bertram (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram resolved ARTEMIS-847.
------------------------------------
    Resolution: Abandoned

There's been no movement here for the last 5 years or so. It looks to me like there's no longer interest in implementing this. Please re-open if plans change. Thanks!

> Reservations via REST API
> -------------------------
>
>                 Key: ARTEMIS-847
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-847
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>          Components: Broker
>            Reporter: John D. Ament
>            Assignee: John D. Ament
>            Priority: Major
>
> This is an over arching goal to build out a reservation based API for messaging.  Right now this is a summary of the thread on the mailing list: https://lists.apache.org/thread.html/fc2c6ebd930b57fcec1590b62376f7e8193223fc87dca2c4a6f4bb69@%3Cdev.activemq.apache.org%3E
> Basically, the idea is to support alternate acknowledgements via the REST API.  The end result should be a highly distributed module that can support querying messages from one server, and acknowledging them on another via a single consumer (session or client id).  Repeated reads of messages should not provide messages already queried for some period of time.  Once the acknowledgement comes in, the message is acknowledged.  Likewise, if its not acknowledged, its eligible for reads again.
> Two broad approaches being discussed:
> - Leveraging the current REST API, add this feature.
> - Rewriting the REST API as a protocol implementation (e.g. artemis-http-protocol) would be better an provide a tighter integration.  It also makes backwards compatibility a smaller issue
> Either way, we need to ensure that any changes in message state are synchronized throughout the cluster (e.g. message in flight, read, etc).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)