"This pattern typically needs a short-lived queue or topic for the application to send responses to. In this scenario, sessions provide a simple alternative solution with comparable semantics."
The above seems to imply that request / response can be achieved with a single queue when using sessions. Is that the case or have I misinterpreted?
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Hi @ntziolis Thanks for reaching out. We will review and update as appropriate.
@ntziolis I have assigned this to content author for further review and update as appropriate.
@ntziolis yes that is correct.
The session id for requests and responses need to be predetermined. All the requests should have the same request session id and then the requestor can acceptSession with the specific response session id.
Understood thank you for the clarification. The reason there that this might not be 100% clear is the sentence in the next paragraph:
The receiver application can process the requests coming in the queue and send replies on a sessions enabled queue, setting the session ID to the unique identifier the sender had sent on the request message.
The ambiguous part being _"send replies on a sessions enabled queue"_, this might be understood as to another session enabled queue.
Instead of _a session enabled queue_ I would suggest to use _the session enabled queue_ to not leave any doubt.
@ntziolis yes, that is great feedback. We will get that done.
@spelluru could you make the edits per @ntziolis recommendation.
@axisc - sure. will do. Thanks.
Updated:
https://docs.microsoft.com/en-us/azure/service-bus-messaging/message-sessions#request-response-pattern