I''m working on a project with a large json api component. We are not ready to upgrade to rails 2 at this point; however, I was wondering if anybody had thought about backporting the rails 2 json serialization back to 1.2.x. I created a quick plugin this morning just of the ActiveRecord and ActiveSupport files involved in the rails 2 json serialization and it seems to work. Has anybody else considered doing this or know of a reason why it might be problematic? Thanks! Will --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Before proper json support was added to the rails trunk, I was using the jsonifier plugin. It worked fine, except with serializing datetimes (but I think that was a problem with rails) On Oct 21, 7:30 am, Will Bailey <will.bai...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> I''m working on a project with a large json api component. We are not > ready to upgrade to rails 2 at this point; however, I was wondering if > anybody had thought about backporting the rails 2 json serialization > back to 1.2.x. I created a quick plugin this morning just of the > ActiveRecord and ActiveSupport files involved in the rails 2 json > serialization and it seems to work. Has anybody else considered doing > this or know of a reason why it might be problematic? > > Thanks! > Will--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
does JSONifier support serialization of included associations and instance methods as the rails 2 code serializer does? On Oct 21, 12:52 pm, eggie5 <egg...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Before proper json support was added to the rails trunk, I was using > the jsonifier plugin. It worked fine, except with serializing > datetimes (but I think that was a problem with rails) > > On Oct 21, 7:30 am, Will Bailey <will.bai...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > I''m working on a project with a large json api component. We are not > > ready to upgrade to rails 2 at this point; however, I was wondering if > > anybody had thought about backporting the rails 2 json serialization > > back to 1.2.x. I created a quick plugin this morning just of the > > ActiveRecord and ActiveSupport files involved in the rails 2 json > > serialization and it seems to work. Has anybody else considered doing > > this or know of a reason why it might be problematic? > > > Thanks! > > Will--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---