<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">2013/10/3 Luca <span dir="ltr"><<a href="mailto:luca800@gmail.com" target="_blank">luca800@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">2013/10/3 Gollum1 <span dir="ltr"><<a href="mailto:gollum1.smeagol1@gmail.com" target="_blank">gollum1.smeagol1@gmail.com</a>></span><br><div class="gmail_extra"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><br>
</div>i semafori...<br>
<br>
<a href="http://www.laurentluce.com/posts/python-threads-synchronization-locks-rlocks-semaphores-conditions-events-and-queues/" target="_blank">http://www.laurentluce.com/posts/python-threads-synchronization-locks-rlocks-semaphores-conditions-events-and-queues/</a><br>
<span><font color="#888888"><br></font></span></blockquote><div>L'avevo trovato proprio questa mattina ma non ho ancora avuto il tempo. Ma visto che č consigliato darā la precedenza.</div></div></div></div></blockquote>
<div><br></div><div> <br></div></div>If you've spent years learning tricks to make your multithreaded code work at all,
let alone rapidly, with locks and semaphores and critical sections, you
will be disgusted when you realize it was all for nothing. If there's
one lesson we've learned from 30+ years of concurrent programming, it
is: <em>just don't share state</em>. It's like two drunkards trying to
share a beer. It doesn't matter if they're good buddies. Sooner or
later, they're going to get into a fight. And the more drunkards you add
to the table, the more they fight each other over the beer. The tragic
majority of MT applications look like drunken bar fights.<br clear="all"><br><a href="http://zguide.zeromq.org/page:all#Multithreading-with-MQ">http://zguide.zeromq.org/page:all#Multithreading-with-MQ</a><br><br>-- <br> .<br>
..: -enrico-
</div></div>