Rodrigo Rosenfeld Rosas wrote: > Rob Nichols wrote: > >> >> Is Rails moving to a pure RESTful design? I don't like REST but love >> Rails. I'd hate to think that as Rails develops it will become more >> difficult to use it RESTlessly. This is just my 2 cents: You have chosen an opinionated framework, you likely knew that when you started using Rails. The point to REST in Rails has little to do with web services, it's about applying convention to the structure of controllers and request routing. REST makes adding a web service API on top of your application easy, but the point is still the convention and not specifically to make web services.
As for me I'm a big proponent of the RESTful design. In other words I happen to agree with the opinion of Rails. That does not mean that you should agree with the opinion yourself. So will Rails continue down the path to RESTful patterns? I'd say the answer to that is very clear. Can you still design your applications today without using the RESTful convention? Sure you can. Will it be more painful? Probably. I would say in your situation: maybe it's time to evaluate whether Rails is "in-line" with your opinion because your individual opinion is not likely to affect the opinions of the core team (who have obviously embraced a RESTful design). "If you've boarded a ship headed toward a destination that you don't want to go, then maybe it's time to start looking for a port where you can board another ship." -- Posted via http://www.ruby-forum.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 [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 -~----------~----~----~----~------~----~------~--~---
