[Bug 24023] [Streams API] Returned promise of write() should be fulfilled with current available space size rather than how many bytes were written

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

--- Comment #2 from Takeshi Yoshino <tyoshino@google.com> ---
(In reply to Takeshi Yoshino from comment #1)
> 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 .

Pasted wrong bug. This is the right one.
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24445

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

Received on Thursday, 30 January 2014 04:28:02 UTC