Uh oh!
There was an error while loading. Please reload this page.
This repository was archived by the owner on Jul 6, 2018. It is now read-only.
This repository was archived by the owner on Jul 6, 2018. It is now read-only.
There was an error while loading. Please reload this page.
Http2Session::destroydoesn't call destroy on its socket, so in order to close a connection completely on the client side,socket.destroy()must be called on the socket exposed by theHttp2Sessionobject.I noticed that
socket.destroycallsdestroyon its parent session (I would've expected the other way around). Is there a reason for doing this?