Implement response-information property for request-response flow.
What does this PR do?
[feature] Updates the executeConnect to return the property response-information in CONNACT if the property request-response-information is set in CONNECT message. The response-information property contains the topic used by the responder to respond to the requester and consequently updates the read access map so that the requester can listen for new PUBLIUSH on that topic.
[test] Extracted common test behavior in AbstractServerIntegrationWithoutClientFixture to share fixture startup of just broker without any client.
Why is it important/What is the impact to the user?
Implement the request-response-information flow used by MQTT5
Checklist
[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have made corresponding change to the default configuration files (and/or docker env variables)
[x] I have added tests that prove my fix is effective or that my feature works
[ ] I have updated the Changelog if it's a feature or a fix that has to be reported
Release notes
Implement response-information property for request-response flow.
What does this PR do?
executeConnect
to return the propertyresponse-information
in CONNACT if the propertyrequest-response-information
is set in CONNECT message. Theresponse-information
property contains the topic used by the responder to respond to the requester and consequently updates the read access map so that the requester can listen for new PUBLIUSH on that topic.AbstractServerIntegrationWithoutClientFixture
to share fixture startup of just broker without any client.Why is it important/What is the impact to the user?
Implement the
request-response-information
flow used by MQTT5Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files (and/or docker env variables)Author's Checklist
How to test this PR locally
Related issues
Use cases