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

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

From: Anne van Kesteren <annevk@opera.com>
Date: Fri, 10 Dec 2010 11:39:43 +0100
To: public-webapps@w3.org, "Web Applications Working Group Issue Tracker" <sysbot+tracker@w3.org>
Message-ID: <op.vnhukh1264w2qv@anne-van-kesterens-macbook-pro.local>
On Fri, 10 Dec 2010 03:24:38 +0100, Web Applications Working Group Issue  
Tracker <sysbot+tracker@w3.org> wrote:
> 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.

Why not queue a task that changes readyState and then dispatches write  
followed by writeend, "synchronously" from the task. That is how a number  
of things work in XMLHttpRequest.


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Friday, 10 December 2010 10:40:18 GMT

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