On 22 August 2011 08:54, Lionel Cons <span dir="ltr"><<a href="mailto:lionel.cons@cern.ch">lionel.cons@cern.ch</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
However, this is not a rhetorical question: a simple STOMP shovel will<br>
read MESSAGE frames in and (re)write them as SEND frames.<br></blockquote><div><br>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).<br>
</div>�<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
IMHO, if RabbitMQ indeed relies on the message-id field, it should<br>
overwrite it and document this behaviour. This way, a user supplied<br>
"message-id" won't create anymore a message that cannot be ack'ed.<br></blockquote><div><br>Agreed. Overwritten, or renamed.<br><br>Tony<br></div></div>