<div>Hi Jay</div><div><br></div><div>Excellent. "epocxy" will certainly help me understand this load regulation principles.</div><div><br></div><div>/Frank</div><div><br><div class="gmail_quote"><div>Le dim. 1 janv. 2017 à 18:38, Jay Nelson <<a href="mailto:jay@duomark.com">jay@duomark.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg">You might want to take a look at <a href="https://github.com/duomark/epocxy" class="gmail_msg" target="_blank">https://github.com/duomark/epocxy</a> for cxy_fount. I gave a talk on this at EUC 2016 (<a href="https://github.com/duomark/epocxy/blob/master/doc/2016-09-09-EUC-Concurrency-Fount.pdf" class="gmail_msg" target="_blank">https://github.com/duomark/epocxy/blob/master/doc/2016-09-09-EUC-Concurrency-Fount.pdf</a>). It provides pace regulation via a reservoir of processes that are gated per 1/100th of a second. You would have to arrange to split your data stream to separate processes, but all the pace regulation is there (and implemented as a behaviour, so you could experiment with alternative pacing approaches).</div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">jay</div><div class="gmail_msg"><br class="gmail_msg"></div></div>_______________________________________________<br class="gmail_msg"><br>erlang-questions mailing list<br class="gmail_msg"><br><a href="mailto:erlang-questions@erlang.org" class="gmail_msg" target="_blank">erlang-questions@erlang.org</a><br class="gmail_msg"><br><a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" class="gmail_msg" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br class="gmail_msg"><br></blockquote></div></div>