Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce a new mode: INDIVIDUAL_ACKNOWLEDGE #328

Open
eolivelli opened this issue Feb 6, 2023 · 5 comments
Open

Introduce a new mode: INDIVIDUAL_ACKNOWLEDGE #328

eolivelli opened this issue Feb 6, 2023 · 5 comments
Milestone

Comments

@eolivelli
Copy link

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:

@OndroMih OndroMih added this to the 3.2.0 milestone Feb 6, 2023
@OndroMih
Copy link
Contributor

OndroMih commented Feb 6, 2023

I think it's the same as this old issue: #178 I'll close the old issue and will keep this new one.

@OndroMih
Copy link
Contributor

OndroMih commented Feb 6, 2023

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?

@eolivelli
Copy link
Author

I know that Tibco-EMS has a similar feature and probably the name is the same

@OndroMih
Copy link
Contributor

OndroMih commented Feb 6, 2023

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 :)

@mattrpav
Copy link

Dupe of #95

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants