23719 2013-11-05 07:47:48 +0000 Consider adding pull style flow control method to Stream 2014-01-28 05:26:11 +0000 1 1 1 Unclassified WebAppsWG Streams API unspecified All All RESOLVED FIXED P2 normal --- 1 tyoshino tyoshino mike public-webapps public-webapps-bugzilla oldest_to_newest 95791 0 tyoshino 2013-11-05 07:47:48 +0000 It's good to have a method to allow "passive producer" (which doesn't want to do work until the connected consumer requests data) to wait until the consumer requests data. E.g. random number generator would be categorized into this group. Consider trade-off between advantage of this feature and inflation of API surface. 95842 1 tyoshino 2013-11-06 06:27:47 +0000 There is a caveat we need to be careful of. If we allow both - Producer waiting for N bytes available for write - Consumer waiting for M bytes available for read this can result in deadlock. Cf. bulk transfer, TCP's silly window syndrome issue. 95963 2 tyoshino 2013-11-07 17:28:47 +0000 Split waiting functionality into a separate method waitForWritable(). It's confusing that write() method has that functionality. It doesn't seem to be worth taking that approach for smaller API surface. For now, include just waitForWritable(undefined). waitForWritable(size) though it might be useful for some cases as explained in Comment 1. 95979 3 tyoshino 2013-11-07 21:17:20 +0000 Done in preview ver https://dvcs.w3.org/hg/streams-api/raw-file/tip/preview.html waitForWritable has been added. 99254 4 tyoshino 2014-01-28 05:26:11 +0000 It's in ED now. Named awaitSpaceAvailable().