Re: [w3ctag/design-reviews] HTML General Review: Web Sockets (#268)

I don't know whether you want feedback from non-TAG members. I work on Chrome's WebSocket implementation. Some quick notes:
* It would have been more convenient if we had a `websocket.ready` property returning a Promise instead of the onopen event.
* The onerror event is useless -- it is the same as onclose with `wasClean === false`.
* The default of `'blob'` instead of `'arraybuffer'` for `binaryType` leads to unpleasant surprises.
* Lack of backpressure is unfortunate. If you can't keep up with the network you run out of CPU or RAM.
* WHATWG Stream support would be nice.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/268#issuecomment-390916928