Hi Raphaël, Changing the version of an API is never just about the version, the implications are more often than not pretty deep.
My take on your case would be to publish your application as the version itself, not clouding each version with overly complex code to handle version specific code and version specific transformations... Right now it might seem as 2 version... how about in 5 years from now... So, instead of having: connect '/rest/simple/v1/:controller/:action/:id' connect '/rest/simple/v2/:controller/:action/:id' You would have: connect '/rest/simple/:controller/:action/:id' in two different applications.... Food for thoughts... but no matter what you determine... post it there so we can all learn for your reflection! have a good day! Jean-Marc http://m2i3.com --~--~---------~--~----~------------~-------~--~----~ 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@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
