Re: [Catalyst] REST - like uri design for CRUD

2008-01-20 Thread Peter Karman
Zbigniew Lukasiak wrote on 1/20/08 1:56 PM: I know this has been discussed already - but I can't find it in the archives. What I conjured is: /class/search /class/id//view /class/id//update /class/create Update and create use really the same logic and templates - so I just forward

Re: [Catalyst] REST - like uri design for CRUD

2008-01-20 Thread Thomas L. Shinnick
At 01:56 PM 1/20/2008, Zbigniew Lukasiak wrote: I know this has been discussed already - but I can't find it in the archives. What I conjured is: /class/search /class/id//view /class/id//update /class/create Update and create use really the same logic and templates - so I just forward

Re: [Catalyst] REST - like uri design for CRUD

2008-01-20 Thread Ashley
On Jan 20, 2008, at 1:33 PM, Thomas L. Shinnick wrote: At 01:56 PM 1/20/2008, Zbigniew Lukasiak wrote: /class/search /class/id//view /class/id//update /class/create spew register=pedant One important topic in the book is that people mix 'verbs' into their URIs when they shouldn't,

Re: [Catalyst] REST - like uri design for CRUD

2008-01-20 Thread Сергей Мартынов
One important topic in the book is that people mix 'verbs' into their URIs when they shouldn't, or at least when they don't _have_ to. Using the book's concepts your URIs would become 1) GET/class?pattern=breadbox 2) GET/class/id/ 3) PUT/class/id/ 4) POST

Re: [Catalyst] REST - like uri design for CRUD

2008-01-20 Thread Christopher Laco
Dave Rolsky wrote: On Sun, 20 Jan 2008, Thomas L. Shinnick wrote: They specifically allow that when PUT is not available or impracticable (clients, firewalls, and proxies can get in the way), you could 'overload' POST by, for example, adding a query parameter _method=PUT to pass-thru the

Re: [Catalyst] REST - like uri design for CRUD

2008-01-20 Thread Dave Rolsky
On Sun, 20 Jan 2008, Thomas L. Shinnick wrote: They specifically allow that when PUT is not available or impracticable (clients, firewalls, and proxies can get in the way), you could 'overload' POST by, for example, adding a query parameter _method=PUT to pass-thru the real request method.

Re: [Catalyst] REST - like uri design for CRUD

2008-01-20 Thread Thomas L. Shinnick
At 04:06 PM 1/20/2008, =?KOI8-R?B?88XSx8XKIO3B0tTZzs/X?= wrote: One important topic in the book is that people mix 'verbs' into their URIs when they shouldn't, or at least when they don't _have_ to. Using the book's concepts your URIs would become 1) GET/class?pattern=breadbox 2)

Re: [Catalyst] REST - like uri design for CRUD

2008-01-20 Thread Daniel Hulme
On Mon, Jan 21, 2008 at 01:06:25AM +0300, Сергей Мартынов wrote: But is the /id/ part of url required? In most cases class would have only one primary identifier, so we can shrink it to GET /class/ - can't we? In this case, we could, but often the identifier for a thing is a character

Re: [Catalyst] REST - like uri design for CRUD

2008-01-20 Thread Dave Rolsky
On Sun, 20 Jan 2008, Ashley wrote: Clipped a bunch. This is great food for thought. I am missing in this scheme how you would know to serve the form for updating. That seems to be the real point of /class/id//update. I suppose that should be /class/id//edit instead and it would, if it

Re: [Catalyst] REST - like uri design for CRUD

2008-01-20 Thread Thomas L. Shinnick
At 04:11 PM 1/20/2008, Ashley wrote: On Jan 20, 2008, at 1:33 PM, Thomas L. Shinnick wrote: At 01:56 PM 1/20/2008, Zbigniew Lukasiak wrote: /class/search /class/id//view /class/id//update /class/create spew register=pedant One important topic in the book is that people mix 'verbs'

Re: [Catalyst] REST - like uri design for CRUD

2008-01-20 Thread Zbigniew Lukasiak
On Jan 20, 2008 10:33 PM, Thomas L. Shinnick [EMAIL PROTECTED] wrote: At 01:56 PM 1/20/2008, Zbigniew Lukasiak wrote: I know this has been discussed already - but I can't find it in the archives. What I conjured is: /class/search /class/id//view /class/id//update