RE: Harvesting REST

Mark,

I am very interested in REST, and in adapting Web services to the Web architecture as much as possible.  But I'd say it depends upon the alignment of the respective use cases, doesn't it?  I mean, I'm not sure the use cases for Web services are the same for the hypertext Web.

I realize this applies to any other architecture we harvest, including CORBA (which to my mind is at least as important to Web services as REST), but that is what will determine the success or failure of our efforts, IMHO.

Eric

-----Original Message-----
From: Mark Baker [mailto:distobj@acm.org]
Sent: Monday, July 15, 2002 8:56 PM
To: www-ws-arch@w3.org
Subject: Harvesting REST



Here's the message I sent to w3c-ws-arch, "harvesting" REST.  It was
really easy, because REST is the result of Roy harvesting the Web.

==snip==

Since REST is so well defined, listing the architectural elements is pretty
easy.  They're already listed here;

http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm

Data elements are; resources, resource identifiers, representation,
representation metadata, resource metadata, control data

Components are; origin server, gateway, proxy, user agent

Connectors are; client, server, cache, resolver, tunnel

"features", as I understand what it is that we're mining, are difficult
to extract from an architecture.  But looking at the Web through REST
eyes, I'd say that the following could be considered features, even
though some are also listed above;

- generic interface
- intermediaries
- stateless interaction
- visibility of messages too all components
- caching
- data streams as arguments

There's probably others.  I can spend some more time digging deeper if
we think that would be useful (and that those are usefully listed as
"features").

MB
-- 
Mark Baker, CTO, Idokorro Mobile (formerly Planetfred)
Ottawa, Ontario, CANADA.               distobj@acm.org
http://www.markbaker.ca        http://www.idokorro.com

Received on Monday, 15 July 2002 21:15:26 UTC