[rabbitmq-discuss] STOMP doesn't include the routing-key on MESSAGE frames

Tony Garnock-Jones tonygarnockjones+rabbitmq at gmail.com
Mon Feb 20 20:36:02 GMT 2012

Hi Steve,

How about the attached patch? It attempts to bring the "destination"
header in MESSAGEs in to line with the STOMP 1.1 spec. I've paid
cursory attention to binary-and-slash-escaping issues but it could use
a second glance before being committed, I reckon.


On 20 February 2012 14:56, Tony Garnock-Jones
<tonygarnockjones+rabbitmq at gmail.com> wrote:
> Adding the routing_key puts the final small missing piece in place. A
> perhaps more STOMPish way of giving it would be to have a "to" header
> or similar carried in a MESSAGE, containing the full destination given
> in the SEND. Oh wait! I've just checked, and actually that's what's
> required by the 1.1 spec already. So the STOMP adapter isn't quite
> spec-compliant, in that it's giving the destination from the
> *subscribe* rather than the *send*.
Tony Garnock-Jones
tonygarnockjones at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: better-destination-patch.patch
Type: application/octet-stream
Size: 3681 bytes
Desc: not available
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120220/38e64056/attachment.obj>

More information about the rabbitmq-discuss mailing list