Marnen Laibow-Koser wrote: > > "Best practices" suggest no such thing that I'm aware of. In a typical > app, most models will have associated controllers. Some controllers > will not have associated models, and a few models may not have > associated controllers. There's no reason to slavishly pair models and > controllers if the nature of the app doesn't call for it. > > Or am I misunderstanding what you meant? >
I meant exactly what you stated.. :) -- 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 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 -~----------~----~----~----~------~----~------~--~---
