Ⓙⓐⓚⓔ wrote:
I'm a bit confused about processData parameter in the ajax call.
From the doc it talks about sending a dom node to the server, that
sounds pretty strange. What is it used for?
From the code it looks like a perfect hook to send non utf-8 data
(iso-8859-1).
Has anyone used
has anyone used it to send an xml doc???
That's what the doc says... I guess I'll just have to try it!
On 6/6/07, Jörn Zaefferer [EMAIL PROTECTED] wrote:
Ⓙⓐⓚⓔ wrote:
I'm a bit confused about processData parameter in the ajax call.
From the doc it talks about sending a dom node to the
I trie $.ajax({
url: /test.cgi,
processData: false,
data: $('html'),
success: function(){console.log(arguments)}
})
and
data: $(html)[0]
both might be what John meant by xml ... no magic
All the encoding is done in $.param using encodeURIComponent. I agree
that it makes sense to modularize that a bit more. Maybe add a
$.encode method like:
$.encode = function(s) { return encodeURIComponent(s) };
That would make it much easier for someone to pop in their own encoder
by simply
very sweet!
On 6/6/07, Mike Alsup [EMAIL PROTECTED] wrote:
All the encoding is done in $.param using encodeURIComponent. I agree
that it makes sense to modularize that a bit more. Maybe add a
$.encode method like:
$.encode = function(s) { return encodeURIComponent(s) };
That would make it
You can already do that now:
encodeURIComponent = function(s) {
// your own encoding
};
But, you know, good luck with that :)
--Erik
On 6/6/07, Mike Alsup [EMAIL PROTECTED] wrote:
All the encoding is done in $.param using encodeURIComponent. I agree
that it makes sense to modularize that
I guess so... but it seems very scary!
On 6/6/07, Erik Beeson [EMAIL PROTECTED] wrote:
You can already do that now:
encodeURIComponent = function(s) {
// your own encoding
};
But, you know, good luck with that :)
--Erik
On 6/6/07, Mike Alsup [EMAIL PROTECTED] wrote:
All the encoding is
7 matches
Mail list logo
