+1 on 1) or 2), though I think I like 1) better. In my view I want to find my object, in this case article 10, which is contained in a container of articles. Then I want to do something with it, namely edit it.
This makes it easy for the view action to be the default, and so can be omitted from the URL, allowing for: http://yoursite/articles/10 Personally I don't like query parameters. They *are* ugly. I can see them being useful for optional special conditions (like turbogearsfmt=json (old example, I know) or for bookmarkable search results, etc. I guess I'm more of a "give me the thing and I'll see what I can do with it", rather than a "I want to do something, give me a thing on which I can do it" kinda guy. ... Err, if that makes sense. And I like clean URLs to match my clean (Python) programming language. :-) Krys Kevin Dangoor wrote: > So, in a generic CRUD feature, what would you want your URLs to look like: > > 1) http://yoursite/articles/10/edit > 2) http://yoursite/articles/edit/10 > 3) http://yoursite/articles/edit?id=10 > > the advantage to the first one is that it makes view look like this: > http://yoursite/articles/10 > > Kevin > > -- > Kevin Dangoor > Author of the Zesty News RSS newsreader > > email: [EMAIL PROTECTED] > company: http://www.BlazingThings.com > blog: http://www.BlueSkyOnMars.com >
