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

Tony Garnock-Jones tonygarnockjones+rabbitmq at gmail.com
Mon Feb 27 15:10:59 GMT 2012


Thanks very much - looking forward to it. (By the way, I just created a
fresh bz account with my gmail address (without the +rabbitmq) - would you
mind adding it to the bug's ACL?)

Regards,
  Tony

On 27 February 2012 05:56, Steve Powell <steve at rabbitmq.com> wrote:

> Tony,
>
> Read your patch, and prefer this solution to adding extra headers.
>
> I'm raising a bug (24763) to fix our spec-compliance problem (thank you for
> pointing this out), and see if we can get this change in.
>
> Steve Powell
> steve at rabbitmq.com
> [wrk: +44-2380-111-528] [mob: +44-7815-838-558]
>
> On 20 Feb 2012, at 20:36, Tony Garnock-Jones wrote:
>
> > 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.
> >
> > Regards,
> >  Tony
> >
> > 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
> > http://homepages.kcbbs.gen.nz/tonyg/
> > <better-destination-patch.patch>
>
>


-- 
Tony Garnock-Jones
tonygarnockjones at gmail.com
http://homepages.kcbbs.gen.nz/tonyg/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120227/13586220/attachment.htm>


More information about the rabbitmq-discuss mailing list