Hey, Wouldn't a simpler, and clearer, solution be to simply admit that using the subordinate namespace of "/users" for things other than user identities is a bad idea?
My first reaction would be to put the "report on users, ordered by popularity" into /user_reports/popularity and be done with it. Of course, I am biased - I'm presently on a major separation-of- concerns kick that's arisen from seeing too many 'canned-report' actions rammed into controllers. Just my 2c... Trev On 31-Jul-07, at 4:44 PM, Michael Koziarski wrote: > >> Naah..my above post doesn't make sense. >> >> May be /users/popular?collection should force going to collection >> method. So if you do something like : >> >> popular_users_url(:force_collection => true) - it should generate >> the above url. > > Sounds a little too tricky for my liking. What we really want is a > way for people to provide a prefix for their collection actions so > that we can distinguish these two cases > > /users/the-prefix/popular > /users/mr-popular > > > -- > 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 -~----------~----~----~----~------~----~------~--~---
