> Does this mean that the default mechanism now changed, so that code
> which used to work will silently start failing?

Yeah, I have some concerns about this. It's great to have $.param
facilitate PHP-friendly serialization, but I'd like to see the default
reversed to avoid breaking existing code.

> The argument that "this helps PHP" could be countered by "this hurts
> java servlets", where request.getParameterValues("a") already returns
> an array for a (as in jQuery < 1.4), but needs to change for jQuery
> 1.4.

This also breaks existing server ASP code, which already understands
that multiple params with the same name should be turned into an
array.

Just another thought here; the flag being added is global, but it's
quite possible a page may be communicating with different hosts that
have different requirements. If different plugins have different needs
then it could get really messy having them bang around the same global
flag.

Either as an alternative or addition to a global flag, .ajaxSettings,
the .ajax() options parameter, .param(), .serialize() and
serializeArray() could support an optional argument to decide how to
serialize the data.



--

You received this message because you are subscribed to the Google Groups 
"jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send email to 
jquery-dev+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/jquery-dev?hl=en.


Reply via email to