Open eolivelli opened 1 year ago
I think it's the same as this old issue: https://github.com/jakartaee/messaging/issues/178 I'll close the old issue and will keep this new one.
The old issue #178 suggested MESSAGE_ACKNOWLEDGE
as the name of this property. @eolivelli, I see that you suggested to name it INDIVIDUAL_ACKNOWLEDGE
, which is already used in Pulsar and ActiveMQ Artemis. Do you know which names for the property are used in other brokers which provide a similar feature?
I know that Tibco-EMS has a similar feature and probably the name is the same
I found this about Tibco: https://docs.tibco.com/pub/api-exchange-gateway/2.2.0/doc/html/GUID-53F882E5-B5F4-4D7D-8E81-00D837EC22AA.html
It looks like their name for the same mode is EXPLICIT_CLIENT_ACKNOWLEDGE
, not the best name IMHO :)
Dupe of #95
Many messaging systems, like Apache Pulsar with Shared subscriptions, support acknowledging single messages. Current Session.CLIENT_ACKNOWLEDGE requires that all the messages dispatched by the session have to be acknowledged and not only that single message.
Some references: