[rabbitmq-discuss] Rejecting messages if incorrect build number

[Patrick Long]

When we move from one major release to another we would like to be able to
consume the old messages from the work queue using the previous version of
the application whilst allowing new messages to be written to the same
queue.

This situation would only occur for a couple of hours after a release.

If we had the buildNumber as a property in a message in theory v2 consumers
could check that the message.buildversion equalled v2 rather than v1

When it did not it the consumer could call Basic.Reject. Perhaps this is
not quite what the AMQP spec intended for the use of Basic.Reject but it
seems like a practical use.

What do others think?

Thanks



-- 
Patrick Long - Munkiisoft Ltd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140321/c23c1bd4/attachment.html>