W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2010

ISSUE-173 (ericu): terminal FileWriter progress events should be queued [File API: Writer]

From: Web Applications Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Fri, 10 Dec 2010 02:24:38 +0000
To: public-webapps@w3.org
Message-Id: <E1PQsf0-0004Bc-BU@lowblow.w3.org>

ISSUE-173 (ericu): terminal FileWriter progress events should be queued [File API: Writer]

http://www.w3.org/2008/webapps/track/issues/173

Raised by: Eric Uhrhane
On product: File API: Writer

When a FileWriter successfully completes a write, currently it:
* dispatches a write event
* sets readyState to DONE
* dispatches a writeend event

If you want to start a new write, you can't do it in onwrite, since readyState is still WRITING.  Those events should be queued for asynchronous delivery, so that readyState is DONE by the time they get handled.  If you set up a new write in onwrite, you'll still run the risk of getting confused by the subsequent writeend from the previous write, but that's detectable.

I'll have to look and see what other events should be marked as queued.
Received on Friday, 10 December 2010 02:24:39 GMT

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