>>I'd like to hear input from others here, and then I'll tell you what I think.
>
>So, what do you think?

I agree with the author. The last 3 or 4 web services I've written started out getting scoped as SOAP services, and for some reason or other, the decision was made to use a simple POST, or even a GET instead. SOAP either added too much fluff (read: bandwidth intensive) to the message for high volume services, or added too much complexity for a simple task. Twice there were circumstances that prevented the use of a toolkit on the client, and so the unnecessary complexity of SOAP really hit home. Out of the 10 or 12 times i've needed to expose a service over the web, SOAP turned out to be the best solution only twice.

I think that the industry as a whole is latching on to SOAP without paying enough attention to what it's costing, and Google's decision to use SOAP instead of a simple GET is a prime example.