> From: Paul Prescod [mailto:]
<snip/>
> But completely orthogonal to that issue is the question of
> the technical
> quality of the SOAP spec itself. SOAP has gradually shifted over the
> years from being a horse (DCOM for the Web) to being a shark
> ("generic,
> transport-protocol-neutral messaging") and I think that today's result
> looks like any other project that shifts focus too quickly for the
> technical architecture to keep up. Floor wax and dessert
> topping. I can
> imagine a person being insanely impressed with the simplicity
> of XML-RPC
> or the sophistication of CORBA but SOAP seems like a horse designed by
> committee.
Yeah, I'm inclined to agree. I liked the simplicity of SOAP 1.1, and liked
its modularity. I started tuning out the web services activity, at some
point, when I started getting a feeling that it was getting out of control.
