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

Any way to generate events on receipt of PUBACK or PUBREC packets? #487

Closed
trev0115 opened this issue Dec 4, 2018 · 5 comments
Closed
Labels
feature-request New feature or request

Comments

@trev0115
Copy link

trev0115 commented Dec 4, 2018

To prove that a subscribed client received the message from a server, it would be nice if the server could raise a event indicating a PUBACK in QOS1 or PUBREC in QOS2 was received. Mostly used for logging. Is this something that could be added to the MqttServer?

@chkr1011
Copy link
Collaborator

chkr1011 commented Dec 4, 2018

So you mean just a plain event (probably containing the application message and client ID as a property) which is fired after every ACK and PUBREC?

@trev0115
Copy link
Author

trev0115 commented Dec 4, 2018

Yeah, that would be perfect.

@trev0115
Copy link
Author

trev0115 commented Dec 4, 2018

When the client connects, I will publish a message with the client's ID and human-readable identifier to the server, storing it in a hashtable. Then when an ACK or PUBREC packet arrives, I can look up the human-readable identifier in the hashtable to display in a log with the topic and payload. This should prove that the client acknowledged receipt of the message from the server.

@SeppPenner SeppPenner added the feature-request New feature or request label Jun 25, 2019
@SeppPenner
Copy link
Collaborator

What's the status of this?

@chkr1011
Copy link
Collaborator

I added this feature and it will be release with version 4.1.x.

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

When branches are created from issues, their pull requests are automatically linked.

3 participants