[rabbitmq-discuss] STOMP & message-id

Tony Garnock-Jones tonygarnockjones+rabbitmq at gmail.com
Mon Aug 22 13:57:03 BST 2011

On 22 August 2011 08:54, Lionel Cons <lionel.cons at cern.ch> wrote:

> However, this is not a rhetorical question: a simple STOMP shovel will
> read MESSAGE frames in and (re)write them as SEND frames.

Interesting. That's a use case that should be considered carefully by all
future designers of messaging protocols, as it's more subtle than it looks
at first glance (as we're seeing now).

> IMHO, if RabbitMQ indeed relies on the message-id field, it should
> overwrite it and document this behaviour. This way, a user supplied
> "message-id" won't create anymore a message that cannot be ack'ed.

Agreed. Overwritten, or renamed.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110822/7479f965/attachment.htm>

More information about the rabbitmq-discuss mailing list