René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add new TCPTransport base class","articleBody":"In [uvloop](https://github.com/1st1/uvloop) (more details [here](https://github.com/python/asyncio/issues/282#issuecomment-155957235)) I implement Transports on top of libuv streams. Here's documentation on [TCP](http://docs.libuv.org/en/v1.x/tcp.html#c.uv_tcp_nodelay) and [general streams](http://docs.libuv.org/en/v1.x/stream.html#api).\n\nStreams are an opaque abstraction over sockets API. All buffering is implemented in the libuv core. There is actually no way to access the underlying socket, which causes some problems. Right now, if you want to set `TCP_NODELAY` or `SO_KEEPALIVE`, the only way is to call `Transport.get_extra_info('socket')` and set them manually.  That's what aiohttp is [doing](https://github.com/KeepSafe/aiohttp/blob/be9ab0e993785ad94bccfd9e4d927858c75bf725/aiohttp/server.py#L30), for instance.\n\nI propose to add a new `Transport` base class - `TCPTransport`. It will have two specific to TCP methods: `set_nodelay(bool enabled)` and `set_keepalive(bool enabled)`.\n\nWithout these methods, it's virtually impossible for me to create a transport that provides this functionality on top of libuv.  This is very similar to how this is done in [Twisted](http://twistedmatrix.com/documents/8.1.0/api/twisted.internet.tcp.Connection.html) and in [Tornado](http://www.tornadoweb.org/en/stable/iostream.html#tornado.iostream.BaseIOStream.set_nodelay).\n","author":{"url":"https://github.com/1st1","@type":"Person","name":"1st1"},"datePublished":"2015-11-12T06:42:29.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/286/asyncio/issues/286"}