On Wed, May 18, 2011 at 12:22 PM, Bill Moseley <[email protected]> wrote: > Quick question, and I hope this doesn't turn into a debate about REST > specifics, just looking for a sane URL scheme. > Say I have an app for managing technical conferences. There's one "user"
Parameters and stuff are all not that important if the parameters are conditions / extra information needed to retrieve/update the resource. In your case I don't think it makes much difference, except for the way you will handle your parameters in the controllers. The important ideas about REST URLs is that they do not contain verbs but always point to a resource. Resources are nouns and are usually used plural for collections and singular for a silgle resource. Parameters are fine IMHO and even encouraged so long as the params are not verbs of course ;-) _______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
