You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, its impossible to create a proper net.Conn wrapper for *websocket.Conn as you cannot implement a SetDeadline method that interrupts a pending read without bricking the connection.
See golang/go#15224 for why a set deadline method that interrupts the connection is useful
The text was updated successfully, but these errors were encountered:
This is going to be pretty much impossible as if we have a large write or read, we cannot unblock it without bricking the connection because net/http only gives us a io.ReadWriteCloser for dials.
This idea overall seems rather janky. I can't think of when it's a good idea to actually run an arbitrary protocol over WebSocket's like this. If you want to run a protocol over HTTP, just use HTTP Connect. If you are for some reason limited to a browser, you probably shouldn't be running an arbitrary protocol over WebSocket's and this library won't really help you anyway because you're on the browser.
At the moment, its impossible to create a proper net.Conn wrapper for *websocket.Conn as you cannot implement a SetDeadline method that interrupts a pending read without bricking the connection.
See golang/go#15224 for why a set deadline method that interrupts the connection is useful
The text was updated successfully, but these errors were encountered: