<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body dir="ltr" bgcolor="#ffffff" text="#000000">
<p style="margin-bottom: 0cm; margin-top: 0pt;">The reason we are using
a message queue is to be able to send various messages to perform
actions in an async manner.</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;"><br>
</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;">I prefer not to lose
these messages, hence the durable queue, but I can recover from not
getting them.</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;"><br>
</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;">The behavior I would
expect, such as flowing back to the disk is to flush them to the disk
and only keep a small portion in-memory, when "the cows come home" (or
more exactly, the cowboy comes back and pushes the cows to their
rightful place) it will start reading from the disk chunk by chunk
until it reaches a point where all the backlog finished and from there
it will go back to work as it was before.</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;"><br>
</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;">Having that combined
with a key that says when we should start throwing things directly to
the disk without keeping them in memory (or without keeping them in
memory too much) as well as a max queue length (depth, depends on where
you look at it) would be really great.</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;"><br>
</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;">Having the ability to
write a queue plugin would be really great. There is always that 20%
that requires a certain behavior that is not off the shelf :-)<br>
</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;"><br>
</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;">Eran </p>
<p style="margin-bottom: 0cm; margin-top: 0pt;"><br>
</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;">Ben Hood wrote:</p>
<blockquote
cite="mid:269388e30809110438o7a2a809dr4ea9742f6e04f59b@mail.gmail.com"
type="cite">
<pre wrap="">Eran,
On Thu, Sep 11, 2008 at 12:14 PM, Ben Hood <a class="moz-txt-link-rfc2396E" href="mailto:0x6e6562@gmail.com"><0x6e6562@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">You've got 2 options:
</pre>
</blockquote>
<pre wrap=""><!---->
You might also have a third option: setting the auto-delete flag. By
setting this flag, when the consumer goes away, the queue will be
auto-deleted and hence the messages will be dropped.
ATM, I assume you have a durable queue that you are sending persistent
messages to. Does this necessarily fit in with the nature of your
application from a design perspective? Do you *really* need persistent
messages for stuff that you are apparently not interested in
consuming?
Off on a tangent, this *may* be a use case for pluggable queues. If
you implemented a queue backend that overflowed to disk, then you
could happily queue up messages until the cows come home. Or at least
until your SAN fills up. Again, this could be a future feature.
HTH,
Ben
</pre>
</blockquote>
<br>
</body>
</html>