W3C home > Mailing lists > Public > www-ws-arch@w3.org > May 2003

RE: Magic

From: Anne Thomas Manes <anne@manes.net>
Date: Sun, 18 May 2003 09:26:27 -0400
To: "Mark Baker" <distobj@acm.org>, "Jim Webber" <jim.webber@arjuna.com>
Cc: <www-ws-arch@w3.org>
Message-ID: <ECEDLFLFGIEENIPIEJJPMEGJEEAA.anne@manes.net>

So let's carry this example to something a bit more applicable to the real
world. Let's say order processing. The traditional SOA folks (i.e. RPC
heritage) would normally create a single service with a single URI that
exposes about 20 operations to do all kinds of things with orders. Users of
this service must include the PO ID number with all calls and they must
indicate a method name indicating what should be done.

In a RESTful example, you would have a different URI for each PO number. You
use the "new PO" URI to obtain a new URI for your PO. Then you use PUT on
the PO URI to submit the order, and GET on the PO URI to return it's state
(the PO plus its current status). Another PUT would submit changes.

Okay -- that takes care of the basic CRUD operations -- but order processing
involves a lot more than CRUD operations. So please, Mark, can you provide
us a real-world example? One that lets us do thinks like aggregate
information about orders by customer, back order status, payment terms,
geographical region, etc?

Regards,
Anne


> -----Original Message-----
> From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
> Behalf Of Mark Baker
> Sent: Saturday, May 17, 2003 7:01 PM
> To: Jim Webber
> Cc: www-ws-arch@w3.org
> Subject: Re: Magic
>
>
>
> On Sat, May 17, 2003 at 08:38:32PM +0100, Jim Webber wrote:
> > I suspect this is not feasible for everyone to do. However, if the REST
> > contingent would perhaps post a simple application somewhere we could
> > download, install, and marvel at it perhaps some of these
> issues would go
> > away. Or at least the non-REST crowd could argue on a more
> informed basis.
>
> I like my lightbulb example.  It's worked on two previous occasions to
> give folks epiphanies;
>
> GET on a URI returns "0" or "1" depending on the state of the bulb.
> PUT on that same URI with "0" turns the bulb off, "1" turns it on.
>
> That's it, at least to get your head around state transfer, and past
> the mistaken assumption that the Web is for humans.
>
> I recommend followups to www-ws@w3.org too.
>
> MB
> --
> Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
> Web architecture consulting, technical reports, evaluation & analysis
>   Actively seeking contract work or employment
>
Received on Sunday, 18 May 2003 09:26:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:19 GMT