- From: Anne van Kesteren <annevk@opera.com>
- Date: Wed, 24 Aug 2011 10:33:43 +0200
- To: "Charles Pritchard" <chuck@jumis.com>
- Cc: "WebApps WG" <public-webapps@w3.org>
On Tue, 23 Aug 2011 20:44:15 +0200, Charles Pritchard <chuck@jumis.com> wrote: > Is there any interest in supporting application/x-www-form-urlencoded ? > > It would of course lose any carried content types or file names from > Blobs. urlencoding is certainly inefficient, and it's something that can > be done in JS as things currently stand. > It would help to send urlencoded posts to services that don't support > multipart. Examples of such services would be useful here. (That would still accept urlencoded files.) > Prpoposed: > > FormData output with the x-www-form-urlencoded mime type: > formData.toUrlEncodedBlob(xhr.send) > > If going down the blob path, these two would have the same end-result: > formData.toMultipartBlob(xhr.send) > xhr.send(formData); What kind of API-style is this? -- Anne van Kesteren http://annevankesteren.nl/
Received on Wednesday, 24 August 2011 08:34:34 UTC