W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2009

Re: File API Feedback

From: timeless <timeless@gmail.com>
Date: Wed, 1 Jul 2009 12:53:25 +0300
Message-ID: <26b395e60907010253i23ccbddeoec18ca58bee54cc9@mail.gmail.com>
To: Garrett Smith <dhtmlkitchen@gmail.com>
Cc: Jonas Sicking <jonas@sicking.cc>, arun@mozilla.com, Boris Zbarsky <bzbarsky@mit.edu>, Ian Hickson <ian@hixie.ch>, Anne van Kesteren <annevk@opera.com>, WebApps WG <public-webapps@w3.org>
On Wed, Jul 1, 2009 at 2:22 AM, Garrett Smith <dhtmlkitchen@gmail.com> wrote:
> The picasa-style example mentioned earlier uses the word "upload".
> I've not used Picasa, but it appears to read files off a local
> network.

confused. i suspect i was the one who mentioned it.

Picasa is mostly a local application. One can do a large number of
operations with it.

among them:
1. select a number of local files
2. get previews (in some file formats that might be possible by
sampling, e.g. an interlaced image format)
3. rotate
4. color correct (etc.)
5. upload

in the case of getting previews and doing manipulations (which are
actually done in two passes, a fast pass on the preview, and then an
expensive background pass on the underlying data), these are local
operations where portions of a file would be sufficient in certain
stages. And it definitely would make sense to be able to upload a
large file in chunks.

I'm glad to see the API under discussion is growing support for ranges.

Note of course that whatever API supports ranges needs to ensure that
the data isn't forcibly coerced into valid Unicode, as the underlying
data for an image can include all sorts of patterns which aren't valid
UTF8/16/....
Received on Wednesday, 1 July 2009 09:54:14 GMT

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