Yanick a écrit : > ... hmm.. hun ? so, what about back compatibility ? Is this new > response object will be compatible with older versions of Prototype, > or yet another script refactoring is to expect ?
It will be entirely backward-compatible: you'll still get responseText as always, still get all the methods you used to call on the raw transport (XHR) object, and still get unsanitized JSON on X-JSON as default. But you'll be able to get much more power out of it. We never break backward compatibility unless we're absolutely compelled to (e.g. major security fix). And when we do, we provide a deprecation layer (as you'll see for upcoming DOM/position refactoring) for ~6 months, so people can adjust at their own pace. -- Christophe Porteneuve a.k.a. TDD "[They] did not know it was impossible, so they did it." --Mark Twain Email: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" 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/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
