<p>Hopefully it doesn't use select if no timeout is set...</p>
<p>--Guido van Rossum (sent from Android phone)</p>
<div class="gmail_quote">On Mar 14, 2012 2:08 AM, "Antoine Pitrou" <<a href="mailto:solipsis@pitrou.net">solipsis@pitrou.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, 14 Mar 2012 04:26:16 +0000<br>
Kristján Valur Jónsson <<a href="mailto:kristjan@ccpgames.com">kristjan@ccpgames.com</a>> wrote:<br>
> Hi there.<br>
> I want to mention some issues I've had with the socketserver module, and discuss if there's a way to make it nicer.<br>
> So, for a long time we were able to create magic stackless mixin classes for<br>
> it, like ThreadingMixIn, and assuming we had the appropriate socket<br>
> replacement library, be able to use it nicely using tasklets.<br>
<br>
I don't really think the ability to "create magic stackless mixin<br>
classes" should be a driving principle for the stdlib.<br>
I would suggest using a proper non-blocking framework such as Twisted.<br>
<br>
> So, my first question is: Why not simply rely on the already built-in timeout<br>
> support in the socket module?<br>
<br>
In case you didn't notice, the built-in timeout support *also* uses<br>
select().<br>
<br>
Regards<br>
<br>
Antoine.<br>
<br>
<br>
_______________________________________________<br>
Python-Dev mailing list<br>
<a href="mailto:Python-Dev@python.org">Python-Dev@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/python-dev" target="_blank">http://mail.python.org/mailman/listinfo/python-dev</a><br>
Unsubscribe: <a href="http://mail.python.org/mailman/options/python-dev/guido%40python.org" target="_blank">http://mail.python.org/mailman/options/python-dev/guido%40python.org</a><br>
</blockquote></div>