REST: everything old is new again?

Mike Dierken mike@DataChannel.com
Mon, 27 Aug 2001 12:15:14 -0700


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C12F2C.99D0D0B0
Content-Type: text/plain;
	charset="iso-8859-1"

> 
> > What bothered me before and still bothers me is the implication
> > that by transforming to REST, all issues of interface complexity
> > go away.  I don't buy that.  Indeed, knowing how to tell someone
> > how to call an RPC call is difficult.  However, doing a GET or
> > POST on a URI is just as difficult: how do I form the URI?
> 
> You don't, in most cases.  You're provided it.  It's opaque.
> 
I think this needs a page in the Wiki.
 - how is it provided?
 - does the client have to parse lots of markukp?
 - how do I know what parts of the markup I'm looking for?


------_=_NextPart_001_01C12F2C.99D0D0B0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">



RE: REST: everything old is new again?



>
> > What bothered me before and still bothers me is the implication
> > that by transforming to REST, all issues of interface complexity
> > go away.  I don't buy that.  Indeed, knowing how to tell someone
> > how to call an RPC call is difficult.  However, doing a GET or
> > POST on a URI is just as difficult: how do I form the URI?
>
> You don't, in most cases.  You're provided it.  It's opaque.
>
I think this needs a page in the Wiki.
 - how is it provided?
 - does the client have to parse lots of markukp?
 - how do I know what parts of the markup I'm looking for?

------_=_NextPart_001_01C12F2C.99D0D0B0--