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

As suggested by Domenic, I read this whole thread and I still have to digest it because I still haven't thought about the possible implications of the implementations in WebKit, which is the one that I am doing.

Some questions remain open though (maybe I read too fast and skipped some important matters and I misunderstood the whole thing). I think the introduction of ReadableByteStream, though logical because of efficiency reasons, might disrupt a bit the idea of having a common interface to read data and specially the way we would pipe that data to other streams. Would we need to create WritableByteStreams and would they operate only with ReadableByteStreams or will we just let the loosily typed JavaScript do its magic and let a common WritableStream deal with the ArrayBuffer coming from a ReadableByteStream and let the garbage collector act after that? I think I require a bit of clarification for my understanding here.

About the read()+ready() vs the promise based read() implementation, I have no preference, both make sense to me (though it is true we would have to reimplement the second option)

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