[ https://issues.apache.org/activemq/browse/AMQ-748?page=all ]
Nathan Mittler closed AMQ-748:
------------------------------
Resolution: Fixed
Fixed.
> Add request-id and response-id headers to STOMP connect/connected handshake
> ---------------------------------------------------------------------------
>
> Key: AMQ-748
> URL: https://issues.apache.org/activemq/browse/AMQ-748
> Project: ActiveMQ
> Type: New Feature
> Components: Transport
> Reporter: Nathan Mittler
> Assignee: Nathan Mittler
> Priority: Minor
> Fix For: 4.1
>
> Original Estimate: 1 week
> Remaining: 1 week
>
> For the new activemq-cpp library, we need to extend the STOMP
> connect/connected handshake so that we get back a response-id for our
> response correlator. To do this, we need to send something in the connect
> request that contains a client-defined request-id. My first thought was to
> just reuse the message-id header, but that is typically reserved for cases
> when a client is expecting to acknowledge a message. So rather than risk
> breaking that paradigm, I propose a new header "request-id" that is just used
> on the connect message. When the broker receives a connect request with a
> request-id header, it creates a connected response with a response-id set to
> the request-id of the original request. This way the client can treat the
> handshake as a true request/response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
