On 3/16/07, Tom Gregory <[EMAIL PROTECTED]> wrote: > > > This problem didn't exist (at this volume level) until Prototype started > serializing Forms as Hashes instead of query strings
What problem? I thought we were merely discussing about conventions and which to embrace/discard. ... which led to the problem of figuring out how to represent two inputs > with the same name When Prototype serialized forms to query string, those two inputs looked like this: "foo=1&foo=2" .. and nobody complained. Now that we serialize using Hash.toQueryString , the same form inputs look like this: "foo=1&foo=2" ... and everybody complains! Suddenly you all want to replace the whole thing with JSON! :) Remember, we've covered form serialization a long time ago. It works. Now we're just polishing and trying not to break stuff. On 3/16/07, Colin Mollenhour <[EMAIL PROTECTED]> wrote: > > why can't Ajax.Request leave the parameters option a string if it is > passed a string? Then we would need to branch the logic around hacks into hacks for strings and hacks for hashes---obviously not a good way to code. String params are only for backwards compatibility, you really should handle it with hashes. Using hashes internally in the framework has slimmed down both Ajax params and Form serialization code, and it should reduce the number of string hacks in user code, also. It's also much nicer to look at. The change had regressions, unfortunately. Version 1.5.1 is going to fix all the issues we know of, though. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
