Author j1m
Recipients gvanrossum, haypo, j1m, yselivanov
Date 2016-06-29.13:56:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1467208617.65.0.407826469958.issue27392@psf.upfronthosting.co.za>
In-reply-to
Content
Guido, IMO, there's value in having the ability to accept connections independently of handling them.

It wasn't clear to me from reading the documentation that create_connection is only meant for making client connections, especially given that it can take an already connected socket.  It works well for non-SSL server sockets and would work for SSL with a trivial change.

This issue was discussed on the tulip list or issue tracker a couple of years ago. (Sorry, I can't find the link ATM.) I think it was dismissed because no one felt like looking into it and because you asserted that it makes no sense to use an async library when handling each connection in a separate thread.

IMO, async loop is useful even for a single connection when reading and writing are not purely synchronous. In ZEO it's very useful that that the server can send data to a client independent of requests the client is making.  (Technically, under the hood this often means that there are really 2 I/O channels, the client's TCP connection and whatever mechanism the loop uses to allow itself to be woken asynchronously as in call_soon_threadsafe.)
History
Date User Action Args
2016-06-29 13:56:57j1msetrecipients: + j1m, gvanrossum, haypo, yselivanov
2016-06-29 13:56:57j1msetmessageid: <1467208617.65.0.407826469958.issue27392@psf.upfronthosting.co.za>
2016-06-29 13:56:57j1mlinkissue27392 messages
2016-06-29 13:56:56j1mcreate