Rabbitmq offers persistent messaging over durable exchanges and queues, so I don't see where you are missing anything :-)
On Fri, Mar 25, 2011 at 6:32 PM, Oren Shomron <[email protected]> wrote: > I have the exact same issue - I need 100% reliable message delivery, and I'm > not interested in coding my own local persistent message queue for the cases > when Rabbit is unavailable. There's a lot of extra complexity involved, and > I'm surprised the framework doesn't handle this as it seems it would be > relevant in many-a-project. > - Oren > _______________________________________________ > rabbitmq-discuss mailing list > [email protected] > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss > > -- You received this message because you are subscribed to the Google Groups "rabbitmq-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rabbitmq-discuss?hl=en.
