- From: Adam Rice <notifications@github.com>
- Date: Fri, 17 Nov 2017 04:13:41 +0000 (UTC)
- To: whatwg/streams <streams@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 17 November 2017 04:14:04 UTC
ricea commented on this pull request. > @@ -245,8 +245,11 @@ For readable streams, an underlying source can use this desired size as a backpr generation so as to try to keep the desired size above or at zero. For writable streams, a producer can behave similarly, avoiding writes that would cause the desired size to go negative. -Concretely, a queueing strategy is given by any JavaScript object with a <code>highWaterMark</code> property and a -<code>size()</code> method. <!-- TODO: https://github.com/whatwg/streams/issues/427 --> +Concretely, a queuing strategy is given by any JavaScript object with a <code>highWaterMark</code> property. For byte +streams the <code>highWaterMark</code> always has units of bytes. For other streams the default unit is <a>chunks</a>, +but a <code>size()</code> function can be included in the strategy object which returns the size for a given chunk. This This wasn't actually intentional: I delete the text and rewrote it :-) -- 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/pull/856#discussion_r151600046
Received on Friday, 17 November 2017 04:14:04 UTC