I strongly recommend not following the second article for REST interfaces. REST is considerably different from RPC; regular API design patterns do not apply since you operate on resources rather than calling functions.

- David


On 22.02.2010, at 10:25, Simon Thulbourn wrote:

Here's a page explaining REST a bit better: http://tomayko.com/writings/rest-to-my-wife and a PDF for designing APIs: http://chaos.troll.no/~shausman/api-design/api-design.pdf

– Simon

On 22 Feb 2010, at 10:08, Simon Cornelius P Umacob wrote:

On Mon, Feb 22, 2010 at 5:02 PM, David Zülke
<[email protected]> wrote:

GET /products - list
GET /products?num=100&page=2 - this is how you use query strings properly, /products/100/2 or so would *not* be RESTful as it doesn't represent a
resource

Yikes, I didn't know that.  In order to make this RESTful, do we need
to use /products/num/100/page/2 instead?  What's the general rule for
creating "beautiful" RESTful URLs? =)

[ simon.cpu ]

_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users

_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users

Reply via email to