> I have an enhancement proposal for the REST handling in Rails. I personally don't think this approach is worth the trouble unless you have a scenario where you have many HTML UIs accessing the same base model. Basically, this is the two-step view as defined by http://www.martinfowler.com/eaaCatalog/twoStepView.html.
The common use case given is a airline ticketing system that's shared by multiple airlines in an alliance. All use the same fundamental system, but they each implement their own UI layer on top of it. I don't see this as a generally applicable model for Rails. As in not something "most people need most of the time". But do wrap this up as a plugin that extends Rails in the points you feel are necessary to support this better. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
