Re: Why XML to comunicate Distributed Components?

On 27 feb, 20:30, "andrew queisser" <andrew.queis...@xxxxxx> wrote:
"carofe" <carlosr...@xxxxxxxxx> wrote in message

news:13b64c37-dbeb-4814-88bc-527d2d42beaf@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



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?

XML has some features as self-described, human-readable, etc..., and
there are many tools for validation and parsing.
Those features are very useful for Configuration files and
Descriptions file which could be edited by humans.
But, Are those features necessaries to communicate two components? Is
it necessary that communication between two component being human-
readable?
About self-described:
Self-described messages is useful for computing, I mean, validations,
infering, etc... But, Is it necessary the message in Plain Text
format?.
Which are the benefit of use XML to communicate components?

I think you already answered your question. XML has the benefits you mention
above but if the two components that exchange data don't require a
self-describing, human-readable and character based format why would you
incur the overhead of formatting and parsing the data? If you don't care
about human-readable you can go to binary XML or similar. If you don't care
about self-describing you can just send your data structures as raw bytes.
If you go to a binary format you have to keep endian and alignment issues in
mind, of course.

Andrew

Hi Andrew:
I mean Binary communication between component but based on existing
communication platform like CORBA, RMI, etc...
I have designed and implemented complex distributed systems for two
years ago based on WebServices and co. technologies (WS-*, SAML,
etc...) with successful result. But until today, I've not found any
case with the real needs of SOAP (or other XML-based) message format
in communications. I've not found out the benefit of XML Plan Text
yet, but only performance issue.
.

Relevant Pages

  • Re: Why XML to comunicate Distributed Components?
    ... technology as message format. ... Why the communication between components should be ... XML has some features as self-described, human-readable, etc..., and ... about self-describing you can just send your data structures as raw bytes. ...
    (comp.object)
  • Re: Why XML to comunicate Distributed Components?
    ... technology as message format. ... Why the communication between components should be ... XML is unreadable, at least by normal human beings. ... Validation is not a proper argument here, because it is not the semantics ...
    (comp.object)
  • Why XML to comunicate Distributed Components?
    ... the purposing of this post is to find good reason about xml ... technology as message format. ... Why the communication between components should be ... Are those features necessaries to communicate two components? ...
    (comp.object)
  • Re: Why XML to comunicate Distributed Components?
    ... technology as message format. ... Why the communication between components should be ... The primary advantage to using XML is that it is a standard. ... In nearly every other way XML is a pretty poor mechanism for serializing data. ...
    (comp.object)
  • Re: Sane Syntax
    ... vital role in the future of TeX but we need some more human friendly ... Generating well formed LaTeX2e documents from XML ... Another approach is to convert existing documents to XML format and go ... TEI, together with DocBook, are the two ...
    (comp.text.tex)