Re: Why XML to comunicate Distributed Components?

Responding to Carofe...

Well, the purposing of this post is to find good reason about xml
technology as message format.
My question is: Why the communication between components should be
XML?

Because ASCII is portable. XML just happens to be the ASCII language for describing state data that won the Standards War.

<Hot Button>
Computing today pays a horrendous penalty for portability because the computer hardware vendors cannot standardize on things like endian, lsb location, alignment, floating point format, etc.. Applications have to encode/decode between ASCII and binary representations in every distributed context. Worse, they are forced to used highly inefficient ASCII character parsing, searching, etc..

The advent of ubiquitous interoperability and distributed processing drives the need for portable state data. The resulting ASCII processing is a substantial contributor to the fact that today one needs a desktop that is equivalent to a 1984 mainframe in power just to run the same spread*** that ran quite well on an Apple II in 1984.
</Hot Button>



--
There is nothing wrong with me that could
not be cured by a capful of Drano.

H. S. Lahman
hsl@xxxxxxxxxxxxxxxxx
Pathfinder Solutions
http://www.pathfindermda.com
blog: http://pathfinderpeople.blogs.com/hslahman
"Model-Based Translation: The Next Step in Agile Development". Email
info@xxxxxxxxxxxxxxxxx for your copy.
Pathfinder is hiring: http://www.pathfindermda.com/about_us/careers_pos3.php.
(888)OOA-PATH
.

Quantcast