Message270133
How about we use connect_socket() or a variant on that name? That feels similar to connect_{read,write}_pipe(), which also take a protocol_factory and an already-opened I/O object.
If it's only for server-side sockets I'd call it connect_server_side_socket() -- I don't care that the name is long, the use case is not that common. Or we could have connect_socket() with a server_side flag and a server_hostname argument, and refactor some things so that it shares most of its implementation with _create_connection_transport(). |
|
Date |
User |
Action |
Args |
2016-07-10 20:40:41 | gvanrossum | set | recipients:
+ gvanrossum, vstinner, j1m, yselivanov |
2016-07-10 20:40:41 | gvanrossum | set | messageid: <1468183241.0.0.272427979434.issue27392@psf.upfronthosting.co.za> |
2016-07-10 20:40:40 | gvanrossum | link | issue27392 messages |
2016-07-10 20:40:40 | gvanrossum | create | |
|