Re: [streams] ReadableStream.getReader name is a bit misleading (#308)

>From a dev point of view, getReader is really 'lock the stream and get me
the thing that will allow me to access to the data'. The thing is called a
reader and its lifetime is controlled with releaseLock.

I would really avoid using getXXX in case one can never get the same JS
object through this method. The notion of locking seems more important to
convey.

The single-reader is a nice meta-model but I doubt users will actually have
that in mind.
   Y
Le 30 mars 2015 20:30, "Domenic Denicola" <notifications@github.com> a
écrit :

> Yeah, @wanderview <https://github.com/wanderview> covered my point of
> view pretty nicely. Even though it does get a new one each time it's
> (successfully) called, "conceptually" only one "real" reader exists per
> stream. The mapping of that conceptual reader to JS objects is not
> one-to-one though.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/whatwg/streams/issues/308#issuecomment-87781718>.
>


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