[Catalyst] RFC: Catalyst::Controller::REST::DBIC

[luke saunders]

On Mon, May 5, 2008 at 5:19 PM, J. Shirley <jshirley at gmail.com> wrote:
> On Mon, May 5, 2008 at 8:18 AM, Andrew Rodland <arodland at comcast.net> wrote:
>  > On Monday 05 May 2008 09:50:08 am J. Shirley wrote:
>  >  > On Mon, May 5, 2008 at 4:31 AM, Matt S Trout <dbix-class at trout.me.uk> wrote:
>  >  > > On Sun, May 04, 2008 at 09:06:30AM -0700, J. Shirley wrote:
>  >
>  > > >  I fail to see how whether the PK is the lookup key or not has any
>  >  > >  relevance at all to the original point, which was "your lookup key and
>  >  > >  names of actions might clash so it can be nice to have an extra path
>  >  > > component such as 'id' for the lookup part to disambiguate".
>  >  >
>  >  > Because I'm talking about REST and a verb in the URI doesn't need to be
>  >  > there.
>  >
>  >  But those nouns you're talking about aren't verbs at all.
>  >
>  >  Andrew
>
>  How is /create, /edit or /delete not a verb?
>  My argument is separate to the /create is valid in the /foo/{token}
>  bit.  I'm saying that /foo/create is silly to have in the first place ...

Okay, let me clear this up. Originally the plan was to have a
centralised REST-style action which dispatched POST/PUT/GET/DELETE
requests to the appropriate actions while also providing RPC-style
verb actions as an alternative for use if the client didn't properly
support the REST request methods. Having listened to discussion in
this thread I think it would be better to make the module pure REST
and then provide the RPC alternative through a subclass, perhaps also
integrating Catalyst::Request::REST::ForBrowsers into the REST version
as suggested.

>  If you apply actual REST principles, you don't have such nonsense.
>  But again, as I said, this is if you are working with REST.  If REST
>  doesn't fit your application model, don't use it.  Just don't name
>  things REST when they are really CRUD.

Why can't CRUD be RESTful?

In fact my revised plan is to glue together a base REST module and a
base CRUD module and add the list method discussed somewhere else in
this thread to provide a complete default RESTful module. Ideally the
REST base module could be swapped for an RPC style base module to
easily provide an RPC alternative of the same thing.