On Tue, 23 Aug 2011 20:44:15 +0200, Charles Pritchard <[email protected]>
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/
