On 1-Aug-07, at 4:17 AM, Tom Ward wrote:
> > Am I horribly misguided in wanting to use plural and singular prefixes > to distinguish between collections and individual entities?: > Tom, I don't think it's horribly misguided - it's an idea that's been chucked around quite a lot and iirc the source of some disagreement. While it does solve the issue at hand, it has a couple of negative side-effects (for me anyhow). Namely, I like my URLs to be 'hackable' in that users should be able to lop off the 'tomafro' from: /users/tomafro and get a list of users. Splitting up the singular vs plural either breaks that or (if you allow /user to refer to the collection as well) re-introduces the same ambiguity. There's also the issue of what a url looks like for an uncountable name - right now the impact of an uncountable resource name is hidden from the user (:singular => 'fish_instance' for example). Under your scheme that would be exposed in the URL. On balance, I'm not a fan of the strategy. Trev > Collections: > > /posts/tagged/ruby > /posts/from/2007/12 > /posts/written-by/tomafro > /users > > Individual items: > > /user/tomafro > /post/1 > > Tom > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
