I believe you should refactor your app to rails 3.1 and then build a nice API.
2011/12/2 Rog <[email protected]> > I have a question about refactoring, I just joined a company with a > rails 2.3 code-base (pretty large and not many tests) this site has a > user facing site, but the bulk of the functionality is for the admin > facing portion of the site, I want to build a nice API with OAuth as > well as make it easier to maintain and push the user facing portion > forward, should I just try to build it on top of the existing rails > 2.3, should I create a new site for the user and api portion on top of > rails 3.1 (not sure how I would share the models and other logic > between the two though), or some other method? ANy best practices > here? > > -- > 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 [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-talk?hl=en. > > -- *Taffarel de Lima Oliveira (Taffarelo3)* * * *Desenvolvedor Web* -- 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 [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-talk?hl=en.
