OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Re: [xml-dev] REST as RPC done right

[ Lists Home | Date Index | Thread Index ]

> Is it fair to describe REST as RPC done right?

I could pick nits, but won't.  Sure, it's fair.

The expressiveness of GET/PUT/POST/DELETE is enormous of course,
but HTTP and REST *do* support the addition of other methods.
So it's really more RPC like than even I like to suggest. 8-O

The architectural constraint that components have identity is
important, but OORPC also has that.  The additional constraint
that makes all the difference is that the methods must be
generic and apply to *all* things with identity, unlike OORPC
where methods were specific to each thing.

For example, if you had a dog, OORPC would model it as;

interface dog
{
 getName();
 getBreed();
 pet();
 walk();
 feed();
}

whereas REST models it as;

interface
{
  GET()
  PUT()
  POST()
  DELETE()
  [other method name]
}

(you knew that, I was just describing it for others)

MB
-- 
Mark Baker, Chief Science Officer, Planetfred, Inc.
Ottawa, Ontario, CANADA.      mbaker@planetfred.com
http://www.markbaker.ca   http://www.planetfred.com




 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS