Comments on: REST: What’s it good for? Part Deux http://decafbad.com/blog/2002/04/26/oooabg It's all spinning wheels and self-doubt until the first pot of coffee. Fri, 19 Mar 2010 00:06:39 +0000 hourly 1 http://wordpress.org/?v=3.0-alpha By: pb http://decafbad.com/blog/2002/04/26/oooabg/comment-page-1#comment-62 pb Thu, 01 Jan 1970 00:00:00 +0000 http://www.decafbad.com/blog/?p=107#comment-62 <p>Why not POST/GET requests with key=value pairs as a response. Done. Forget the PUT and DELETE. You're just making a function call. Forget XML formatted response since so few environments come with XML parsing. The average function call returns so little data that key=value pairs are more than adequate. And everyone already knows how to do this stuff.</p> Why not POST/GET requests with key=value pairs as a response. Done. Forget the PUT and DELETE. You’re just making a function call. Forget XML formatted response since so few environments come with XML parsing. The average function call returns so little data that key=value pairs are more than adequate. And everyone already knows how to do this stuff.

]]> By: Christopher Heschong http://decafbad.com/blog/2002/04/26/oooabg/comment-page-1#comment-63 Christopher Heschong Thu, 01 Jan 1970 00:00:00 +0000 http://www.decafbad.com/blog/?p=107#comment-63 <p>pb, how do you represent arrays? Or multi-dimensional arrays? Or note that something is an integer instead of a string?</p> pb, how do you represent arrays? Or multi-dimensional arrays? Or note that something is an integer instead of a string?

]]> By: Mark Baker http://decafbad.com/blog/2002/04/26/oooabg/comment-page-1#comment-64 Mark Baker Thu, 01 Jan 1970 00:00:00 +0000 http://www.decafbad.com/blog/?p=107#comment-64 <p>deus_x, that's pretty much exactly right. The only clarification I'd make is that you might POST an email address (in plain text, or application/x-www-form-urlencoded, or XML if you want) to http://myhost/promotion/players in order to create a new player. That POST could return a HTTP 201 response with the Location header set to the URI of that new player (if it succeeded).</p> <p>MB</p> deus_x, that’s pretty much exactly right. The only clarification I’d make is that you might POST an email address (in plain text, or application/x-www-form-urlencoded, or XML if you want) to http://myhost/promotion/players in order to create a new player. That POST could return a HTTP 201 response with the Location header set to the URI of that new player (if it succeeded).

MB

]]> By: l.m.orchard http://decafbad.com/blog/2002/04/26/oooabg/comment-page-1#comment-65 l.m.orchard Thu, 01 Jan 1970 00:00:00 +0000 http://www.decafbad.com/blog/?p=107#comment-65 <p>pb: </p> <p>Well, that's exactly how I did things with flash games-- POST/GET requests with key/value pairs which responded with key/value pairs. Like Christopher says, this started to fall apart when I needed richer data structures.</p> <p>As for REST, it seems that their idea is to not make function calls. What you do with REST is to treat URIs more like database resources, on which you perform SELECT (GET), INSERT (POST), UPDATE (PUT) and DELETE (DELETE). So instead of calling an award_points method on my player object, I UPDATE (PUT) points on the points resource of my player (represented by URI).</p> pb:

Well, that’s exactly how I did things with flash games– POST/GET requests with key/value pairs which responded with key/value pairs. Like Christopher says, this started to fall apart when I needed richer data structures.

As for REST, it seems that their idea is to not make function calls. What you do with REST is to treat URIs more like database resources, on which you perform SELECT (GET), INSERT (POST), UPDATE (PUT) and DELETE (DELETE). So instead of calling an award_points method on my player object, I UPDATE (PUT) points on the points resource of my player (represented by URI).

]]>