« Return to Thread: Our REST implementation

Re: Our REST implementation

by Davey Shafik-3 :: Rate this Message:

Reply to Author | View in Thread

This isn't quite true, and I spoke to Ben about this too.

The point of Zend_Rest_Server is to help mapping
requests to *existing* (read: used elsewhere) code. Or at least
code consistent with a project.

The Zend_Rest_Server should *not* be modified, but I have
no problems with building something *on top* that is more RESTy.

But in all honesty, REST is about making requests and getting responses,
those responses have to be generated somehow, so its RPC, no matter how
it happens.

The point of Zend_Rest_Server is that Zend_Rest_Client can automate
those REST calls
using a programmatic local API.

- Davey

Shahar Evorn wrote:

> Hi all,
>
> I had the chance to listen to Ben Ramsey's talk about REST last week in
> IPC07. During the talk, Ben explained the REST model / philosophy, and
> mentioned that our Zend Framework implementation of Zend_Rest_Server is
> in fact not RESTFul, but more RPC style.
>
> I did some more reading on this and it really does seem that our
> Rest_Server is more RPC oriented (eg. method focused and not resource
> focused) web service implementation.
>
> I was going to propose a redesign of our REST server, which will be
> similar to a front controller router / dispatcher implementation,
> mapping URLs to classes which contain a method / action for each HTTP
> "verb" (GET, POST, PUT, DELETE). I think this could be a base for a
> simple, light and elegant implementation.
>
> Before I do that, I would like to hear your opinions about this, as I am
> not too experienced with REST and I have a general feeling that there is
> no real "standard" we can follow here.
>
> Shahar.
>
>  

 « Return to Thread: Our REST implementation