W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013

Re: Multi-GET, extreme compression?

From: Nicolas Mailhot <nicolas.mailhot@laposte.net>
Date: Wed, 27 Feb 2013 15:40:55 +0000 (UTC)
To: ietf-http-wg@w3.org
Message-ID: <loom.20130227T162930-922@post.gmane.org>
Julian Reschke <julian.reschke@...> writes:

> 
> On 2013-02-27 11:16, Nicolas Mailhot wrote:
> > James M Snell <jasnell@...> writes:
> >
> >
> >> Fair enough
> >
> > There is a similar need for mput/mpost, the fact current web apps require
> > a separate user sequence for each file a user wants to publish/attach to a
> > message is one of the few remaining use-cases where they suck compared to
> > local apps.
> 
> But that's UI (HTML/JS), not protocol, right? Also, that's solvable; I 
> happen to be in a project where our web app supports bulk upload of 
> files by drag & drop to the browser window...

That's just another workaround, where you paper over the missing feature with
gobs of site-specific javascript and by pretending the average user
drag-and-drops files in apps. I've seen the same demoware years ago it does not
work out in real life.

The average user does not drag and drop he uses the file selector, that maps to
standard html forms, that maps to what the protocol knows to do (one element at
a time). In browsers the file selector is restricted to single file selection to
respect what non-js-extended http/html ecosystem allows.

And, lastly, most web app developpers will not bother with loads of feel-good js
workarounds since what the users want is their default file selector, not some
kind of js emulation.

-- 
Nicolas Mailhot
Received on Wednesday, 27 February 2013 15:41:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 February 2013 15:41:45 GMT