[Bug 23790] Remove size argument from read() and introduce pullAmount attribute instead

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

--- Comment #2 from Takeshi Yoshino <tyoshino@google.com> ---
(In reply to Takeshi Yoshino from comment #1)
> Since we cannot install a hook which is invoked right after fulfill callback
> is run, a user cannot decrease pullAmount on completion of one read().
> 
> pullAmount = 1024
> ...
> readPromise is fulfilled with 512 bytes
> Fulfill callback is run asynchronously
> Inside fulfill callback we run this
>   pullAmount = 512
> But at this point, underlying IO may be already instructed to fetch 1024
> bytes of data.
> 
> We should enable gradual decrease of pullAmount?

Until next read() call, the number of bytes used for fulfilling the last read()
call should occupy the pullAmount.

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

Received on Monday, 11 November 2013 19:41:31 UTC