Hi Mark,<br><br>On 12 August 2012 15:58, Mark Feeney <span dir="ltr"><<a href="mailto:mark.feeney@gmail.com" target="_blank">mark.feeney@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Most of the tasks that get queued are of the "never lose this" variety<br>
(durable everything, persistent messages).<br></blockquote><div><br>Emile has already given some sensible advice, and since you've been writing your own database-backed pseudoqueues you probably have a pretty good handle on this anyway, but in case it helps I wrote a little on options for task queueing (for the special case of "transactional" tasks, but most of the ideas generalise) using RabbitMQ last year: <a href="http://www.eighty-twenty.org/index.cgi/tech/rabbitmq/tasks-within-transactions-20111218.html">http://www.eighty-twenty.org/index.cgi/tech/rabbitmq/tasks-within-transactions-20111218.html</a><br>
<br>Regards,<br> Tony<br></div></div>-- <br>Tony Garnock-Jones<br><a href="mailto:tonygarnockjones@gmail.com" target="_blank">tonygarnockjones@gmail.com</a><br><a href="http://homepages.kcbbs.gen.nz/tonyg/" target="_blank">http://homepages.kcbbs.gen.nz/tonyg/</a><br>