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

Adding CONNACK data to the 'connected' callback. #1503

Open
fpagliughi opened this issue Jul 12, 2024 · 0 comments
Open

Adding CONNACK data to the 'connected' callback. #1503

fpagliughi opened this issue Jul 12, 2024 · 0 comments
Milestone

Comments

@fpagliughi
Copy link
Contributor

fpagliughi commented Jul 12, 2024

It would be really helpful if the "connected" callback passed the CONNACK data back to the application (connection present flag, reason code, properties, etc).

This is particularly vital with v5 clients using auto reconnect. With v3, if the session was initially present on the server, you could safely assume the session is still there after a reconnect (or so I've always assumed). But with v5, if the client specifies a session expiry interval, the existing session could disappear before the reconnect completes.

I assume we can't repurpose the unused "cause" pointer, as that might cause some horrific crashes in people's apps. So maybe we can create a new connectedWithData callback, or something like that?

Perhaps another new feature for v1.4?

@icraggs icraggs added this to the 1.4.0 milestone Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants