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

Request / Response: Formalize the request/response pattern within MQTT #829

Open
Tracked by #695
andsel opened this issue Apr 20, 2024 · 0 comments
Open
Tracked by #695
Assignees
Labels

Comments

@andsel
Copy link
Collaborator

andsel commented Apr 20, 2024

Formalize the request/response pattern within MQTT and provide the Response Topic and Correlation Data properties to allow response messages to be routed back to the publisher of a request. Also, add the ability for the Client to get configuration information from the Server about how to construct the response topics.

Implementation

Implement the management of response information header in CONNACK. When a client send a CONNECT with request response information property set, the server reserve a subtree of the subscription topic so that client can receive response publishes for request-response flow.
The server reserve a subtree specific for the connecting (requester) client, for example /reqresp/reponse/<client id> and configure read access for the client, and write access for the rest (*). This is needed to automatically provide a response topic configured with correct access rights.

@andsel andsel changed the title Request / Response: Formalize the request/response pattern within MQTT and provide the Response Topic and Correlation Data properties to allow response messages to be routed back to the publisher of a request. Also, add the ability for the Client to get configuration information from the Server about how to construct the response topics. Request / Response: Formalize the request/response pattern within MQTT Apr 20, 2024
@andsel andsel self-assigned this Apr 20, 2024
@andsel andsel added the mqtt5 label Apr 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant