Mike Deem wrote:
> That is what I want from SOAP. I want use SOAP to build distributed
> systems based entirely on message passing. Dealing with all messages in
> exactly the same way makes doing this simpler. Using XML as the message
> format has lots of benefits that I don't think are in dispute.
[...]
> If, when all is said and done, I'm left with something that
> should be called "XML Services" or "XML Internet Services," instead of
> "XML Web Services," I really don't care.
Why do I have this vision of XML as ASCII, SOAP as TCP/IP,
and IIS/Apache/.NET as inetd? We seem to be going from inscrutable
binary (even bit-oriented) formats to nearly-inscrutable textual
formats; from programming and scripting languages to "orchestration"
languages; and from #include files to WSDL.
To steal a page from Len, "meet the new boss, same as the old boss."
--
Kian-Tat Lim, , UTF-7: +Z5de+pBU-
