> What I do like about hamptons proposal is that he's indicating he wants > the most basic resource facilities.
Definitely, I think it's a great idea to come up with a nice evolutionary enhancement to the resources code, along with some added metadata for reflecting on what's going on. > However, instead of baking this in the ActionController I think > resources deserve to be first class citizens. This idea was actually > born by Dan Yoder after long discussions on the Waves project. The term > "resource controller" that most are using is a misnomer, the two should > be decoupled imo. I think that this kind of experimentation should definitely take place in a plugin. The controller + routes thing we have now works really well, and some minor enhancements could well improve that. Something larger like you're talking about here should be left in plugins till it's had a chance to prove itself and get fully baked. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-core@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
