Keith Moore wrote:

A realization of RPC, yes. That's the point. Let's keep using it. I would have assumed that was what web architecture was about. If it's about building the next IDL compiler, my advice is to save some time. We have plenty to choose from already.

HTTP as a substrate for creating new RPC interfaces? Why? Haven't we developers been through enough of them? The web is something different.

IMHO, it's much more familiar to a lot of newer developers, like all the novices who cut their teeth on the web. The problem, if you want to call it one, is that most of these developers don't know they're using designs based on REST, let alone what REST means. And yes, these applications overruse POST because they aren't really fully designed around these concepts, and partly because of browser realities.

But once you move into web services (real ones, not SOAP), the browser constraints disappear and suddenly using all four methods the way they should be used becomes an option, and I see no reason not to go ahead and use them. If SOAP won't support me in that, I don't see much reason to do anything but ignore it, unfortunately.