Lists Home |
Date 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;
whereas REST models it as;
[other method name]
(you knew that, I was just describing it for others)
Mark Baker, Chief Science Officer, Planetfred, Inc.
Ottawa, Ontario, CANADA. firstname.lastname@example.org