websocketstream-explainer

websocketstream-explainer copied to clipboard

Assuming #12 is resolved in favour of keeping `close()`, it would be good if it returned a promise.

ricea

Remove close() method?

1

`close()` serves four purposes: 1. Abort the handshake. However, the `signal` passed in the constructor options can also do this. 2. Pass `code` and `reason` to a Close frame after...

ricea

Support for ping/pong frames

1

The WebSocket API is quite awkward in regard to ping/pong frames. It would be great if WSS could support them. Has there been any thoughts regarding that?

crowlKats

Making WebSocket.send() reliable

4

Hello, WebSocketStream is a great proposal to solve backpressure and cases where sockets are overflown with too many messages. The extension mechanism will also bring needed improvements to WebSockets. However...

ea167

ricea

This would permit users some control over the trade-off between throughput and rapid backpressure detection.

ricea

Basic auth, cookies and client certificates cause a lot of problems for WebSockets. It would be nice to have an option to turn them off. Unfortunately, I don't think we...

ricea

Custom headers into handshake

1

Please allow developers to pass custom headers into the constructor so they can, for example, provide an `Authorization` header.

adrianhopebailie

Better spec for how close() / cancel() and the closing promise should act

5

How is `close()` expected to behave if the user stopped reading the ReadableStream but there are a few messages in the queue up for grabs? If you try to implement...

etodanik

See https://github.com/WICG/direct-sockets/issues/18 where the direct sockets API is trending in that direction. It might be best if everyone aligned.

domenic