- From: Garrett Smith <dhtmlkitchen@gmail.com>
- Date: Sun, 24 Aug 2008 23:25:33 -0700
- To: "Maciej Stachowiak" <mjs@apple.com>
- Cc: "Oliver Hunt" <oliver@apple.com>, "Web Applications Working Group WG" <public-webapps@w3.org>
Oliver, Maciej - have you given this any thought? I'd like to get some discussion going for this. I'll write the failing tests, but I need some vendor input. That goes for Jonas, Boris, and other Mozilla guys, too. Thanks, Garrett On Tue, Aug 12, 2008 at 10:23 PM, Garrett Smith <dhtmlkitchen@gmail.com> wrote: > On Tue, Aug 12, 2008 at 8:01 PM, Maciej Stachowiak <mjs@apple.com> wrote: >> >> On Aug 11, 2008, at 11:21 PM, Garrett Smith wrote: >> > > [snip] > >>> Why don't you post up your ideas? >> >> We'll probably make a proposal for async reads in time. Our initial >> implementation in WebKit only lets you upload a File object via XHR but we >> believe eventually some form of direct I/O should be added. >> > > I have a few questions and an idea. > > Does calling send( file ) generate the appropriate Content-Type > request header with matching boundary? > > How can this feature be detected? > > Idea: > How about passing a form to send? When passing a form to send, the > correct headers are set from the form's enctype, generating the > boundary, content-disposition and other stuff for multipart requests. > > The only problem is that it complicates send with much functionality. > Responsibly adaptive and well designed web apps will want to creat > feature tests and fallback strategies, but this will be awkward and > difficult to do, given the current API. Why not create a separate > method - sendForm. > > if(xhr.sendForm) > xhr.sendForm(form); > > > Garrett > >> Regards, >> Maciej >> >> >> >> >
Received on Monday, 25 August 2008 06:26:08 UTC