<br><br><div class="gmail_quote">2011/8/1 Emile Joubert <span dir="ltr"><<a href="mailto:emile@rabbitmq.com">emile@rabbitmq.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
The other possibility is to provide your own browsable queue<br>
implementation. This is not a trivial undertaking, but it is possible to<br>
slot in your own implementation and make it free from FIFO restrictions.</blockquote></div><br>Would it be easier to implement queue event nofications ("messages was put to the queue", "messages was confirmed")?<br>
<br>Also, if messages not stored in mnesia, how are they stored then? In our case we don't really need a perfectly consistent snapshot<br>of what's in the queue, just something that is reasonably up to date and won't result in message reordering (that's why basic.get with requeueing is not an option).<br clear="all">
<br>RabbitMQ offers 95% of what we need, this is the last 5%. So please help me a little with this :)<br>-- <br>MK<br><br><a href="http://github.com/michaelklishin" target="_blank">http://github.com/michaelklishin</a><br>
<a href="http://twitter.com/michaelklishin" target="_blank">http://twitter.com/michaelklishin</a><br><br>