On 1/22/07, Colin Mollenhour <[EMAIL PROTECTED]> wrote: > > This change, while I think is a good idea in general, will be somewhat > difficult to make use of if the new JSON object replaces the old JSON > object. >
You have a point there. I didn't think people would care, but you have convinced me they could. Your idea of writing to the "json" property of the xhr object is not bad. Alternatively, there could be a "getJson()" method that lazily evaluates "responseText". --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
