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 much easier for someone to pop in their own encoder by simply overwriting $.encode. MIke On 6/6/07, Ⓙⓐⓚⓔ <[EMAIL PROTECTED]> wrote: > 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 happens! > > data: 'foo=Jörn', > gave me: > foo=J%C3%B6rn > > > data: 'foo='+ escape('Jörn'), > > gave me > foo=J%F6rn > which looks like pretty good ascii encoding.. ! > > perhaps we need an alternate $.serialize for these non-utf users??? > > > On 6/6/07, Ⓙⓐⓚⓔ <[EMAIL PROTECTED]> wrote: > > 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 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 it??? > > > Its possible to send an XML document via XmlHttpRequest, at least it > > > should be. To stop attempts at serializing that document, you can set > > > processData to false. > > > > > > -- > > > Jörn Zaefferer > > > > > > http://bassistance.de > > > > > > > > > > > > > > -- > > Ⓙⓐⓚⓔ - יעקב ʝǡǩȩ ᎫᎪᏦᎬ > > > > -- > Ⓙⓐⓚⓔ - יעקב ʝǡǩȩ ᎫᎪᏦᎬ
-- Ⓙⓐⓚⓔ - יעקב ʝǡǩȩ ᎫᎪᏦᎬ