Sorry for the delay, it took me a while to read http://code.google.com/p/tulip/source/browse/ and wrap my head around it. On Thu, Jan 24, 2013 at 8:50 PM, Guido van Rossum <guido at python.org> wrote: > What other things might you want to do with the socket besides calling > getpeername() or getsockname()? >From http://en.wikipedia.org/wiki/Berkeley_sockets#Options_for_sockets > Options for sockets >> After creating a socket, it is possible to set options on it. Some of the more common options are: >> TCP_NODELAY disables the Nagle algorithm. > SO_KEEPALIVE enables periodic 'liveness' pings, if supported by the OS. Though these may not be the concern of a protocol as defined by PEP 3156. Would that be reasonable to expect > from a protocol written to be independent of the specific transport > type? >>Most protocols should be written independent of transport. But it seems to me that a user might write an entire app as a "protocol". Yuval Greenfield -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-ideas/attachments/20130127/9aedcbff/attachment.html>