W3C home > Mailing lists > Public > public-device-apis@w3.org > March 2010

Re: New draft of FileWriter API posted

From: Eric Uhrhane <ericu@google.com>
Date: Mon, 8 Mar 2010 18:49:49 -0800
Message-ID: <44b058fe1003081849w493a81acnd75eaa20bcb301d9@mail.gmail.com>
To: Anne van Kesteren <annevk@opera.com>
Cc: public-device-apis@w3.org
On Mon, Mar 8, 2010 at 6:42 AM, Anne van Kesteren <annevk@opera.com> wrote:
> On Sat, 06 Mar 2010 03:01:13 +0100, Eric Uhrhane <ericu@google.com> wrote:
>>
>> I've just posted a new draft of the File Writer API [1], based on the
>> version I posted in January [2].  I look forward to your feedback.  In
>> the mean time, I'll get going on a clean draft of the FileSystem API.
>
> BlobBuilder should have an overloaded append() method rather than two
> separate methods. That would be more consistent with similar APIs.

Will do.

> It is not defined how the constructor for BlobBuilder ought to work.

I can flesh that out, but there's not a lot to say.  Do you mean
something more than a line like this?
"When the BlobBuilder() constructor is invoked, the user agent MUST
return a new BlobBuilder object."

> Why is endings needed? Can't the author handle that himself?

He can emulate a specific platform.  If we want him to be able to
emulate "native", we'd have to tell him what filesystem he's actually
writing to, which I'd like to avoid.  I'm trying to make it easy to
share files with apps external to the browser.

> Could we get away with not having encoding at all? I.e. always writing UTF-8
> octets?

That's certainly an easy place to start.  Anybody have strong feelings about it?

    Eric
Received on Tuesday, 9 March 2010 02:50:40 GMT

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