Message242195
> As for replacing the protocol but keeping the transport, what would
> be the semantics of that?
The protocol is not really replaced, it's wrapped.
Before:
SocketTransport <- UserProtocol
After:
SocketTransport <- (asyncio.sslproto.SSLProtocol
<- asyncio.sslproto._SSLProtocolTransport) <- UserProtocol
That way, the same SocketTransport (but it could be something else, e.g. a pipe transport) is always bound to the event loop; we simply insert a processing layer in the chain between the original transport and the final protocol. There are two distinct objects so that the SocketTransport sees a protocol and the UserProtocol sees a transport; but those two objects work hand in hand. |
|
Date |
User |
Action |
Args |
2015-04-28 18:26:09 | pitrou | set | recipients:
+ pitrou, gvanrossum, vstinner, asvetlov, yselivanov, Elizacat, gc |
2015-04-28 18:26:09 | pitrou | set | messageid: <1430245569.41.0.173396108911.issue23749@psf.upfronthosting.co.za> |
2015-04-28 18:26:09 | pitrou | link | issue23749 messages |
2015-04-28 18:26:09 | pitrou | create | |
|