- From: Takeshi Yoshino <notifications@github.com>
- Date: Thu, 31 Mar 2016 06:48:16 -0700
- To: whatwg/streams <streams@noreply.github.com>
- Message-ID: <whatwg/streams/issues/433@github.com>
/cc @wanderview @hober @othermaciej @jakearchibald @wolenetz @gwicke @annevk @KenjiBaheux @domenic Hi all, we've finished the last big refactoring around the ReadableStream interface. Only a few editorial and minor naming issues (e.g. https://github.com/whatwg/streams/issues/294) are remaining. The up-to-date spec is available at https://streams.spec.whatwg.org/. You can find usage examples at https://streams.spec.whatwg.org/#rs-intro and https://streams.spec.whatwg.org/#creating-examples. Briefly speaking, the refactoring made the following changes: - (a) addition of byte stream handling API to the existing ReadableStream API - (b) some minor semantic changes (e.g. in which state controller.enqueue() throws) to the ReadableStream API itself Those who are planning to use the Response streaming feature (https://github.com/yutakahirano/fetch-with-streams/issues/63) is affected by (a). The Media Source Extensions standardization (https://github.com/w3c/media-source/issues/14#issuecomment-203582442) is affected by (b). They want to get their appendStream() spec updated soon. So, I'd like you guys to start reviewing the latest ReadableStream API spec and give us your feedback. Please speak up on this thread. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/streams/issues/433
Received on Thursday, 31 March 2016 13:48:46 UTC