boblq wrote:
I have been following the REST Discussion list for some months now. http://groups.yahoo.com/group/rest-discuss/

I just signed up for it last night. Odd that it's on yahoo.

The  http verbs that go a long way are

 GET     get the resource
 POST    create a new resource
 PUT     edit the resource
 DELETE  remove the resource
 HEAD    brief overview of the resource

Which seem to be everything you need to build a basic database with the CRUD features:

Create
Retrieve
Update
Delete


(messy, coupled client) <---REST---> (messy, coupled server)

Yep.

The important point of REST is decoupling the client from the server
thus one gets benefits of scaling and cacheability.

I have been playing with Squid and the CacheFu Zope product. Smart caching can really speed up your website. Note that Zope employs a number of REST concepts. But it also uses cookies and sessions and some other non-RESTful things.

Issues that often come up are sessions (not RESTful) and cookies
(also not RESTful) with observations like:

There are reasons to prefer putting info in URIs instead of cookies:

1. URIs can be bookmarked. Cookies can't.
2. URIs can be linked to. Cookies can't.
3. URIs can be e-mailed. Cookies can't.
4. URIs can be copied and pasted into a different browser. Cookies can't.

If I copy and paste to a friend a URI with my session info encoded in it do they take over my session?

Now finally for an example of how one uses AJAX on the client side with REST to build a responsive application see:
http://www.onlamp.com/pub/a/python/2006/02/23/using-rest-with-ajax.html

This is in my queue of things to read today. I'm thinking I like REST. I am still wondering about AJAX. I'm still not able to come to terms with programming in javascript.

You say you failed. The web appears to some to have been successful. Whose advice should we follow?

Indeed. The proof is in the pudding and this pudding is pretty darn good.

--
Tracy R Reed
http://copilotconsulting.com
1-877-MY-COPILOT


--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to