[
Lists Home |
Date Index |
Thread Index
]
On Mon, Apr 22, 2002 at 03:07:11PM -0400, Didier PH Martin wrote:
> I think that loosely coupled systems are perfect in the case a request for
> data or document is performed. If the document returned is semi-structured
> or not structured then the receivers will need to perform more processing on
> it to make it useful. Otherwise, if the only thing that we need to do is a
> remote action like, for instance, setting a switch to ON, then an RPC is
> well fitted to the job. When I say well fitted, it is simply in terms of
> economies of code.
That's not true. Even by such a narrow definition of "well fitted", a
"document" interface wins out because the code to implement it is
shared with many other resources. Plus it has so many other benefits,
including the biggie, vastly improved visibility.
With REST, you turn a lightbulb on with PUT, because the request is
attempting to explicitly set the state of a resource; the same PUT
used for saving preferences, turning on the TV, or just "editing a
file".
Any task that can be coordinated with RPC, can be coordinated with
REST in a manner more suitable for Internet scale distribution. If
you're doing anything over the Internet with people that you haven't
previously met and may not trust, RPC is the wrong technology.
MB
--
Mark Baker, Chief Science Officer, Planetfred, Inc.
Ottawa, Ontario, CANADA. mbaker@planetfred.com
http://www.markbaker.ca http://www.planetfred.com
|
