W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2011

[FileAPI] Result of calling MultipleReads on FileReader

From: Adrian Bateman <adrianba@microsoft.com>
Date: Tue, 29 Mar 2011 00:37:32 +0000
To: "Web Applications Working Group WG (public-webapps@w3.org)" <public-webapps@w3.org>
CC: "Jonas Sicking (jonas@sicking.cc)" <jonas@sicking.cc>, Arun Ranganathan <aranganathan@mozilla.com>
Message-ID: <104E6B5B6535E849970CDFBB1C5216EB3D263C8A@TK5EX14MBXC138.redmond.corp.microsoft.com>
As we continue to experiment with the File API, I'm trying to understand the
rationale for the Multiple Reads section:
http://dev.w3.org/2006/webapi/FileAPI/#MultipleReads

The spec says:

   If multiple read methods are called on the same FileReader object, user
   agents MUST only process the last call to a read method, which is the
   call that occurs last in a script block that has the "already started"
   flag set [HTML5].

I'm trying to understand the rationale for respecting the LAST call - is it
common for people to call read lots of times and want the last one to be
respected. Since the read happens asynchronously, we'd rather kick off the
read operation as soon as the first read is called and give an error to
subsequent read calls. I'm not sure what the use case is for wanting the last
one (you can always call abort() and start again).

Is there a reason for the current spec text?

Thanks,

Adrian.

-- 
Adrian Bateman
Program Manager - Internet Explorer - Microsoft Corporation
Phone: +1 (425) 538 5111
Email: mailto:adrianba@microsoft.com
Received on Tuesday, 29 March 2011 00:38:06 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:43 GMT