[whatwg] Uploading directories of files

Jeremy Orlow jorlow at chromium.org
Fri Dec 11 02:17:26 PST 2009

On Fri, Dec 11, 2009 at 12:47 AM, Anne van Kesteren <annevk at opera.com>wrote:

> On Fri, 11 Dec 2009 09:33:06 +0100, Markus Ernst <derernst at gmx.ch> wrote:
>> Anne van Kesteren schrieb:
>>> On Fri, 11 Dec 2009 09:13:52 +0100, Markus Ernst <derernst at gmx.ch>
>>> wrote:
>>>> I have no idea how to handle such inconsistent behaviour on the server
>>>> side (except adding extra code to flatten all uploaded directory structures
>>>> before handling). I assume that HTTP upload should be kept simple, and more
>>>> complex upload tasks should be handled with specialized applications, such
>>>> as RadUpload[1].
>>>> [1] http://www.radinks.com
>>> I don't think we want to rely on the availability of Java on the end
>>> user's platform (or the availability of any other plug-in for that matter).
>> I did not mean including it into HTML5 or an UA. Just leaving specialized
>> upload tasks out of the standard, assuming that developers will work with
>> applications that they think are useful for their tasks (and that rely on
>> technologies they believe are avaliable at their target audience).
> And I mean that if it is important to application developers we should make
> it available as a feature and not endorse some plug-in dependency.

I (and I think most of us) strongly agree.  That's the whole point of
standardization.  :-)

Personally, I don't think the case Markus pointed out is at all a show
stopper.  In the case of images, the server could easily recognize and
reconcile duplicates (by hashing them and looking for duplicate hashes or
something).  If the image has been tweaked some in the mean time, the EXIF
data can help.  And so on....this seems like the type of thing clever
developers can work around.

But regardless.....I don't think you could argue that having _some_ path
information is worse than _none_, right?

I also agree with Jonas that if some path information is added, it might be
better to create a new property (other than .name) for it.

And, with or without that extra property, I think what Ian's suggesting
would be useful to users.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20091211/3e191cf4/attachment-0002.htm>

More information about the whatwg mailing list