<div dir="ltr">Ben,<br><br>I think you misunderstood my message. I was saying RabbitMQ should be able to store a non-memory-limited number of <b>persistent</b> messages in the absence of a consumer draining the queue. So to be exact, these would be <b>non-transactional persistent messages</b>. You replied to me about <b>non-persistent</b> messages, which I know are memory-limited. I am confused, because I was at one time (when I was doing my due diligence) convinced that RabbitMQ had no practical limit (other than any set by Mnesia and hard disk space) for storing non-transactional persistent messages. I am simply concerned that perhaps I was mistaken and was asking you to elaborate.<br>
<br>I hope that clears up what I am asking.<br><br>I understand that nobody is forcing me to use the product. I am just trying to establish if I was originally mistaken so that I can take the necessary steps.<br><br>Regards,<br>
Edwin<br><br><div class="gmail_quote">On Thu, Sep 11, 2008 at 8:04 PM, Ben Hood <span dir="ltr"><<a href="mailto:0x6e6562@gmail.com">0x6e6562@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Edwin,<br>
<div class="Ih2E3d"><br>
On Fri, Sep 12, 2008 at 12:59 AM, Ben Hood <<a href="mailto:0x6e6562@gmail.com">0x6e6562@gmail.com</a>> wrote:<br>
> system resource usage. The most it will do is to not acknowledge the<br>
> receipt of a message that it cannot accept the responsibility of<br>
> requeueing should a crash occur.<br>
<br>
</div>Sorry about the atrocious English in that last sentence.<br>
<br>
I meant to say: The most Rabbit will do is to not acknowledge the<br>
receipt of a message for which it cannot accept the responsibility of<br>
requeueing in the event of a system crash.<br>
<br>
HTH,<br>
<font color="#888888"><br>
Ben<br>
</font></blockquote></div><br></div>