[Bug 24023] [Streams API] Returned promise of write() should be fulfilled with current available space size rather than how many bytes were written from bugzilla@jessica.w3.org on 2013-12-06 (public-webapps-bugzilla@w3.org from December 2013)

From: <bugzilla@jessica.w3.org>
Date: Fri, 06 Dec 2013 18:31:38 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-24023-2532-SoLhayc8Q8@http.www.w3.org/Bugs/Public/>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24023

--- Comment #1 from Takeshi Yoshino <tyoshino@google.com> ---
What we really should do is
- consult dataSink (application specific logic) to determine how large (size,
cost) a certain object is.

dataSink (possibly asynchronously) computes the cost of a certain object
written to it. pendingWriteQueue is built based on that cost.

Non real application, generic consumer such as ByteStream introduced in the
spec doesn't know how to compute cost for given object. So, it needs to be
educated via e.g. write()'s second argument as I proposed in
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23977 .

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 6 December 2013 18:31:39 UTC