Message270060
| Author |
yselivanov |
| Recipients |
gvanrossum, j1m, vstinner, yselivanov |
| Date |
2016年07月09日.18:40:43 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1468089643.44.0.657418078077.issue27392@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> wrap_socket implies that it's for wrapping client or server sockets, but it's not. It's only for handling server sockets. Also, I prefer a name that reflects goal, not mechanism.
> I think the name should be discussed over here: https://bugs.python.org/issue27392.
Why can't `wrap_socket` be used for wrapping client sockets? I think we can refactor asyncio to use it in 'create_connection', and maybe to accept new connections.
To my ear, 'asyncio.handle_connection' implies that asyncio will "handle" the connection, i.e. that asyncio itself would do more than just wrapping the socket and attaching a protocol instance. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2016年07月09日 18:40:43 | yselivanov | set | recipients:
+ yselivanov, gvanrossum, vstinner, j1m |
| 2016年07月09日 18:40:43 | yselivanov | set | messageid: <1468089643.44.0.657418078077.issue27392@psf.upfronthosting.co.za> |
| 2016年07月09日 18:40:43 | yselivanov | link | issue27392 messages |
| 2016年07月09日 18:40:43 | yselivanov | create |
|