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

Re: Rename “File API” to “FileReader API”?

From: Robin Berjon <robin@robineko.com>
Date: Wed, 18 Nov 2009 12:07:12 +0100
Cc: public-device-apis@w3.org, public-webapps WG <public-webapps@w3.org>
Message-Id: <E508F415-4523-40A9-97E5-BCA94A5C517F@robineko.com>
To: arun@mozilla.com
Hey Arun,

On Nov 13, 2009, at 11:28 , Arun Ranganathan wrote:
> Discussion about renaming shows that there isn't really consensus about a name change [1][2], so I haven't proceeded with one.  I'd rather proceed without a name change for now, but work towards evolving file write capabilities safely for the web based on this API.  I'm not averse to multiple specifications (and better naming later on), if we find that use cases diverge between groups.  Some editorial help has been forthcoming [3], which is welcome.

I was thinking about this yesterday, and while there's no emergency (it doesn't need to happen before the FPWD), how about:

  File API Level 1: Reading
  File API Level 2: Writing
  File API Level 3: Directories

Arguments:
  - we've already received feedback that people are confused that the API does only reading (even if after hearing the explanation they understand), having it somewhere in the name would help
  - it matches the way we sliced it at the f2f that seemed to garner at least some amount of consensus (and in fact since it seems some who agree with it most violently weren't actually listening at the time :)
  - levels are rather familiar to implementers and authors
  - I do think we can model these as layers of the same API (with different entry points of course)

No need to decide now, it's just an option I wanted to put out there before I forgot.

--
Robin Berjon
  robineko — hired gun, higher standards
  http://robineko.com/
Received on Wednesday, 18 November 2009 11:07:48 GMT

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