jQuery Forum

Ⓙⓐⓚⓔ

has anyone used it to send an xml doc???
That's what the doc says...  I guess I'll just have to try it!
<div><span class="gmail_quote">On 6/6/07, <b class="gmail_sendername">Jörn Zaefferer</b> <<a href="mailto:Enchos@gmx.net">
Enchos@gmx.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ⓙⓐⓚⓔ 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
<a href="http://bassistance.de">http://bassistance.de</a>
</blockquote></div>
<br clear="all">
--
Ⓙⓐⓚⓔ - יעקב   ʝǡǩȩ   ᎫᎪᏦᎬ

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
<div><span class="gmail_quote">
                    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, <b class="gmail_sendername">Ⓙⓐⓚⓔ</b> <<a href="mailto:jakecigar@gmail.com">jakecigar@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
has anyone used it to send an xml doc???
That's what the doc says...  I guess I'll just have to try it!<div><span class="e" id="q_1130329bf7d725e1_1">
<div><span class="gmail_quote">On 6/6/07, <b class="gmail_sendername">
Jörn Zaefferer</b> <<a href="mailto:Enchos@gmx.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Enchos@gmx.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ⓙⓐⓚⓔ 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
<a href="http://bassistance.de" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://bassistance.de</a>
</blockquote></div>
<br clear="all">
</span>
</div><span class="sg">--
Ⓙⓐⓚⓔ - יעקב   ʝǡǩȩ   ᎫᎪᏦᎬ
</span></blockquote></div>
<br clear="all">
--
Ⓙⓐⓚⓔ - יעקב   ʝǡǩȩ   ᎫᎪᏦᎬ

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

very sweet!
<div><span class="gmail_quote">On 6/6/07, <b class="gmail_sendername">Mike Alsup</b> <<a href="mailto:malsup@gmail.com">malsup@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
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, Ⓙⓐⓚⓔ <<a href="mailto:jakecigar@gmail.com">jakecigar@gmail.com</a>> 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, Ⓙⓐⓚⓔ <<a href="mailto:jakecigar@gmail.com">jakecigar@gmail.com</a>> 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 < <a href="mailto:Enchos@gmx.net">Enchos@gmx.net</a>> 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
> > >
> > > <a href="http://bassistance.de">http://bassistance.de</a>
> > >
> > >
> >
> >
> >
> > --
> > Ⓙⓐⓚⓔ - יעקב   ʝǡǩȩ   ᎫᎪᏦᎬ
>
>
>
> --
> Ⓙⓐⓚⓔ - יעקב   ʝǡǩȩ   ᎫᎪᏦᎬ
</blockquote></div>
<br clear="all">
--
Ⓙⓐⓚⓔ - יעקב   ʝǡǩȩ   ᎫᎪᏦᎬ

You can already do that now:
encodeURIComponent = function(s) {
 // your own encoding
};
But, you know, good luck with that :)
--Erik
<div><span class="gmail_quote">On 6/6/07, <b class="gmail_sendername">
Mike Alsup</b> <<a href="mailto:malsup@gmail.com">malsup@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">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, Ⓙⓐⓚⓔ <<a href="mailto:jakecigar@gmail.com">jakecigar@gmail.com</a>> 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, Ⓙⓐⓚⓔ <<a href="mailto:jakecigar@gmail.com">jakecigar@gmail.com</a>> 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 < <a href="mailto:Enchos@gmx.net">Enchos@gmx.net</a>> 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
> > >
> > > <a href="http://bassistance.de">http://bassistance.de</a>
> > >
> > >
> >
> >
> >
> > --
> > Ⓙⓐⓚⓔ - יעקב   ʝǡǩȩ   ᎫᎪᏦᎬ
>
>
>
> --
> Ⓙⓐⓚⓔ - יעקב   ʝǡǩȩ   ᎫᎪᏦᎬ
</blockquote></div>

I guess so... but it seems very scary!
<div><span class="gmail_quote">On 6/6/07, <b class="gmail_sendername">Erik Beeson</b> <<a href="mailto:erik.beeson@gmail.com">erik.beeson@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You can already do that now:
encodeURIComponent = function(s) {
 // your own encoding
};
But, you know, good luck with that :)
<span class="sg">
--Erik
</span><div><span class="q"><span class="gmail_quote">
On 6/6/07, <b class="gmail_sendername">
Mike Alsup</b> <<a href="mailto:malsup@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">malsup@gmail.com</a>> wrote:</span></span><div><span class="e" id="q_11303d967f07a466_4"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
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, Ⓙⓐⓚⓔ <<a href="mailto:jakecigar@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">jakecigar@gmail.com</a>> 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, Ⓙⓐⓚⓔ <<a href="mailto:jakecigar@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">jakecigar@gmail.com</a>> 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 < <a href="mailto:Enchos@gmx.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Enchos@gmx.net</a>> 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
> > >
> > > <a href="http://bassistance.de" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://bassistance.de</a>
> > >
> > >
> >
> >
> >
> > --
> > Ⓙⓐⓚⓔ - יעקב   ʝǡǩȩ   ᎫᎪᏦᎬ
>
>
>
> --
> Ⓙⓐⓚⓔ - יעקב   ʝǡǩȩ   ᎫᎪᏦᎬ
</blockquote></span></div></div>
</blockquote></div>
<br clear="all">
--
Ⓙⓐⓚⓔ - יעקב   ʝǡǩȩ   ᎫᎪᏦᎬ

> You can already do that now:
>
> encodeURIComponent = function(s) {
> // your own encoding
> };
>
> But, you know, good luck with that :)
Well said! :-) Good luck, indeed. The truly brave could try:
encodeURIComponent = escape;
Ha.
Mike