Change makePendingConnection to accept a Stream instead of a Socket #99
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
I'd like to propose the following change: Use a
Stream
argument formakePendingConnection
instead of aSocket
. This allows the use of more general streams, e.g. for a TLS connection. Currently, this is the easiest and cleanest solution since it is not possible to implement something likemakePendingConnection
outside of the websockets library because of thedecodeRequestHead
function, which is a private function from the hidden moduleNetwork.Websockets.HTTP
.This change does break the current API, but I think it is a reasonable change and easy to fix for any users of this function (see e.g. the change in
runApp
).– McManiaC