OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   basic qs - how is xml more flexible for exchanging data?

[ Lists Home | Date Index | Thread Index ]
  • To: xml dev <xml-dev@lists.xml.org>
  • Subject: basic qs - how is xml more flexible for exchanging data?
  • From: Anil Philip <goodnewsforyou@yahoo.com>
  • Date: Thu, 15 Sep 2005 09:58:01 -0700 (PDT)
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=V8GXXrJMZNnLfaiIbh5q7VKEl+8l7CvuEE8n4E89GMY2vNgq/wUinou6Xa6wqJve1i+wknJqEhVO59co5BJ8P9r2vaeht77j0gHKbzn1Jnt51jsPEOUNJ8Cc5VBam4kb875fR/zTS5cWeBqjIx7DcGTkp48vUqTGBcMjuueFKVI= ;
  • In-reply-to: <20050914160159.95764.qmail@web32603.mail.mud.yahoo.com>

Hello,
I would agree that XML is human readable and that
XML+HTML is probably better than HTML. However, I was
wondering:
When we used C, (I guess there's an entire generation
that didnt need to learn it :)), one transferred data
using structs.
eg.
/* from memory... */
struct Foo {
int i;
char[] str;
long j;
};

The Sender and Receiver were tied into explicitly
knowing about Foo's structure - and so were considered
tightly coupled, a bad thing.

With XML, one is sending the description together with
the data in a tagged text file. However, in most cases
of data transfer, the code of both Sender and Receiver
still has to know the structure of Foo especially when
parsing the data file. So how is it more flexible or
even better? (apart from endian stuff)
thanks,
Anil Philip
-

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 




 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS