RE: SOAP breaks HTTP?

> But the point is, GET of a resource makes sense for some things, 
> and in other cases, developers will insist on hiding all of their 
> resources behind an endpoint that exposes *functionality*.  
If the resources are available through functionality (rpc or whatever) then
they are not hidden, they are just not addressable. A pointless and
crippling way to do things.
I bet Paul could write a gateway to make these things addressable with the
published API of the service, so the 'hiding' was ineffective.

I believe that developers will insist on doing this to the dying day of
software itself, but that's boring, and its more fun to show them how to
play with the rest of us.

Received on Tuesday, 26 March 2002 20:06:49 UTC