Re: [w3ctag/design-reviews] WebSocketStream (#394)

> I'm a little unclear on what code using this stream-of-streams model would look like; if you're going down that route, it would be interesting to see an explainer. It sounds like you might be talking about this for a later version of the API.

For reading, something like

```javascript
for await (const message of webSocketStream.readable) {
  for await (const chunk of message) {
    await processChunk(chunk);
  }
  await processEndOfMessage();
}
```
It would probably be good for me to write up a set of proposals for how streaming within a message should work, but I want to get the first iteration of WebSocketStream standardised first.

> Would you like to get more feedback at this stage, or do you think it would be better to wait a bit before taking a closer look at the spec?

At this point I'm waiting for feedback from the origin trial before proceeding with standardisation. While I welcome any input, it would probably be a more efficient use of your time to wait until there is a draft standard.

-- 
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/394#issuecomment-530722654