<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">I would think that LIFO are manageable through in-process publish / subscribe. However, in-the-middle process impacts the performance to compare with native queue implementation. What is you use-case for LIFO?<div><br></div><div>Best Regards, </div><div>Dmitry </div><div><div><br><div><div>On 22 Aug 2014, at 14:50, Jesper Louis Andersen <<a href="mailto:jesper.louis.andersen@gmail.com">jesper.louis.andersen@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 21, 2014 at 4:10 PM, Michael Klishin <span dir="ltr"><<a href="mailto:michael.s.klishin@gmail.com" target="_blank">michael.s.klishin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":1eu" class="a3s" style="overflow:hidden">How would old messages get a chance at being processed at high message<br>
rates, if the order wasn't FIFO? </div></blockquote></div><br>Sometimes, this is actually a bad idea. LIFO mailboxes would be really really cool to have in certain situations.<br><br clear="all"><div><br></div>-- <br>
J.
</div></div>
_______________________________________________<br>erlang-questions mailing list<br><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>http://erlang.org/mailman/listinfo/erlang-questions<br></blockquote></div><br></div></div></body></html>