This repository has been archived by the owner on Sep 13, 2018. It is now read-only.
A way to 'upgrade' protocols #138
Comments
|
My original plan was more or less what you described: implement an "upgrade" wrapper around a transport that spawns a new protocol task w/ the upgraded protocol. Doing this should still be possible, but I don't know how well it would fit in w/ the protocol builders. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There are various needs to be able to upgrade from one protocol to another. Some common ones are 'HTTP1 -> websockets', 'HTTP1 -> HTTP2', `HTTP1 CONNECT -> Anything'.
A possibility could be to simply allow taking a socket (
Io) out of theClientProto/ServerProto, to be bound into another instead.The text was updated successfully, but these errors were encountered: