Re: [w3ctag/design-reviews] Writable Streams (#163)

I guess the `desiredSize` getters on ReadableStreamDefaultController and WritableStreamDefaultController answer that.  Though I'm a little worried about this text:
> At this point in time the division of work between the stream and its controller may seems somewhat arbitrary, but centralizing much of the logic in the controller is a useful structure for the future.

Perhaps this should at least explain the logic of the separation a little bit further so that future spec editors can extend the platform in reasonable ways without messing up the design?

But it's interesting that backpressure itself appears to be signaled just as a boolean.  @travisleithead was wondering how well the backpressure approach here extends to things like media streams, where backpressure might be handled by doing things like reducing resolution rather than by writing the same data more slowly.  Is more than just a boolean backpressure signal needed to handle that?

-- 
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/163#issuecomment-297909069