RE: REST; good for humans and machines

> Imagine opening an IIOP connection to a remote, untrusted server.  What
> method's can you invoke at that point?

Any method which I have credentials to access?

> Now imagine opening an HTTP connection to the same remote, untrusted
> server.  What methods can you invoke then?

Any method which I have credentials to access?

arkin


> 
> That's the difference between transport and transfer, and between layer
> 6 and layer 7.
> 
> > Actually, by your logic, the comparsion of REST to Web services 
> doesn't make sense, either, as they also are defined at different 
> levels of the stack.
> 
> Hmm, no, REST isn't a protocol, it's an architectural style.
> 
> But if you mean that Web services doesn't specify any methods (i.e. does
> not define a coordination language), whereas REST does, then I agree.
> 
> MB
> -- 
> Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
> Web architecture consulting, technical reports, evaluation & analysis
>