W3C home > Mailing lists > Public > public-device-apis@w3.org > November 2009

Re: [FileReader API, ProgressEvents] Design patterns, FileWriter API

From: Anne van Kesteren <annevk@opera.com>
Date: Wed, 18 Nov 2009 10:30:46 +0100
To: arun@mozilla.com, "Marcin Hanclik" <Marcin.Hanclik@access-company.com>
Cc: "WebApps WG" <public-webapps@w3.org>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <op.u3k3dkz564w2qv@anne-van-kesterens-macbook.local>
On Wed, 18 Nov 2009 02:30:16 +0100, Arun Ranganathan <arun@mozilla.com>  
wrote:
> I think that just as the names 'load*' were chosen for generic data  
> transfer events (either networked or within a document), and are used  
> within documents loaded in the DOM, XHR, and FileReader, we'll need  
> reusable 'write*' events.  Without bikeshedding too much, I like your  
> proposal above, but wonder whether we should use the name 'write*' or  
> something else.  Since we already have document.write, 'write' is  
> probably the most vetted string to use here :)

For what it's worth, for XMLHttpRequest "sending" events (which are  
arguably somewhat like write) we still use loadstart/... and simply  
dispatch them on a distinct object. I've no idea what the file writer API  
will look like, but I can imagine we might be able to do the same there.


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Wednesday, 18 November 2009 09:31:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:01 GMT