Re: [streams] How will ReadableByteStream work with seekable resources? (#253)

Actually, I had not thought about `setAllocator()` in the context of a DOM API producing the stream.  I'm not sure we want to make the UA depend on content script to allocate buffers.  Seems like a recipe for a bad time.

Async read seems ok to me, but I think it opens some questions.  What does it do for concurrent read() calls?  Do we allow overlap?  Ordering guaranteed?

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/253#issuecomment-73904953

Received on Wednesday, 11 February 2015 15:55:30 UTC