null
Simon: Keith throws out a complete red herring. I don't see how the RPC spec or the encoding spec are unRESTfull, the only unRESTfull thing in the SOAP spec, is the always POST HTTP binding.
I've been doing some reading on REST. I'm not convinced that REST dictates GET. Here are three quotes from Roy Fielding, the "inventor" of REST:
- REST is an architectural style -- it does not dictate protocol syntax.
- There's no basis for "everything must use GET" in Web architecture.
-
there is a trade-off between GET and POST that usually involves the size of the parameter content.
I'm now convinced that one can architect a system in accordance to the principles of REST and then implement that system using RPC style, HTTP transport, POST binding, SOAP. In fact, I'll go further and state that the GoogleSearch is an instance of this.