Re: Why XML to comunicate Distributed Components?

On 29 feb, 16:42, carofe <carlosr...@xxxxxxxxx> wrote:
On 28 feb, 11:13, shashank <shashank...@xxxxxxxxx> wrote:

On Feb 27, 10:17 pm, carofe <carlosr...@xxxxxxxxx> wrote:

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?

XML files are readable, self-descriptive etc. are not really a reason
for using it for communicating among components build using disparate
technologies.

Mainly because of its inertness to specific processing technology,
(read) by OMG, SUN, Microsoft, IBM etc, it has got more wider
acceptance.

regards,
shashank

You mean, XML language has more acceptance than others language to
standardize some messages interchange protocols and representations of
information to be exchanged.

Well, but why? What is the great benefit or property or feature of XML
which enables it to be the better way?
Why not IDL(for example)?
Tools? Mony? Easy to Understand? The most extensible?

Well, I've found the same discussion here:
http://www.theserverside.com/discussions/thread.tss?thread_id=5122

Thank a lot for yours post
.

Relevant Pages

  • Re: Why XML to comunicate Distributed Components?
    ... Why the communication between components should be ... The protocol has to be simple enough to recognize by a small ... Validation is not a proper argument here, because it is not the semantics ... which is validated, but the XML itself. ...
    (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)
  • Re: Why XML to comunicate Distributed Components?
    ... Why the communication between components should be ... Are those features necessaries to communicate two components? ... Which are the benefit of use XML to communicate components? ... Mainly because of its inertness to specific processing technology, ...
    (comp.object)
  • Re: Why XML to comunicate Distributed Components?
    ... Why the communication between components should be ... XML has some features as self-described, human-readable, etc..., and ... Mainly because of its inertness to specific processing technology, ...
    (comp.object)
  • Re: VS2005 Not ready for prime time
    ... framework classes improvments. ... of features that maximize coding time. ... XML can be almost anything, ... It demanded more knowledge of the developer, ...
    (microsoft.public.dotnet.framework.aspnet)