[rabbitmq-discuss] Published message not queued after publish-ok received when connection quickly closed

Michael Nacos m.nacos at gmail.com
Fri Jul 8 16:17:47 BST 2011


Michael, something like this would be fantastic (and less code to maintain
on my part). any chance of it getting into the RC14?

On 8 July 2011 15:41, Michael Klishin <michael.s.klishin at gmail.com> wrote:

> 2011/7/8 Michael Nacos <m.nacos at gmail.com>
>
>> so, what's currently the best way to publish messages consumed from one
>> queue into another with the amqp gem? This is quite important in processing
>> scenaria when no messages may be lost.
>
>
> Michael,
>
> Does this piece of code look like what you would like to have? An entity
> that consumes messages from one queue and republishes them safely into
> another queue, with a way to transform the message?
>
> https://gist.github.com/1071983
>
> This imaginary AMQP::Rebroadcaster is not that difficult to design and add
> to the amqp gem for RC14 (will be out in a few weeks after
> some more testing with real world apps).
>
> --
> MK
>
> http://github.com/michaelklishin
> http://twitter.com/michaelklishin
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110708/a1a5e46a/attachment.htm>


More information about the rabbitmq-discuss mailing list