[
Lists Home |
Date Index |
Thread Index
]
- To: Michael Kay <mike@saxonica.com>
- Subject: Transmission of XML Data
- From: basudeb gupta <basudeb0001@yahoo.com>
- Date: Mon, 17 Oct 2005 23:33:42 -0700 (PDT)
- Cc: 'xml dev' <xml-dev@lists.xml.org>
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding; b=fIimLFwmzbjpSQV0m4L+Xk+t49v2QoOFcTb4FpJzY3nWPnSRumO9+4GAqi4yWkkrU63tsBmNuwKMTvOzpHCA2H9uaDVz7O0IUHdrLaZAGeiuUe1Lb8p+qX2zh9MY18YsK2AqPcx0xmyC3gvS2p6QgFotZrg5G+Th11r+6l348QU= ;
Hi,
Here is another question of an ignorant person.
How is the XML Data actually exchanged? Is it in its
full glorious expanded form? If so, is it not a great
loss of bandwidth?
If not, I assume there are compression mechanisms
available in the send and receive functions used by
such programs which exchange XML data? Can someone
please guide me on the current state of the art?
I, coming from working on a protocol called SIGCOMP,
feel strongly that an exchangeable compression
decompression format may also be quite suitable for
XML data exchange.
Am I redreaming the wheel?
Thanks
Basudeb
--- Michael Kay <mike@saxonica.com> wrote:
> > Somehow, to me, XML does not solve any more
> problem
> > than comma delimited files would do.
>
> If your problems are confined to simple tabular
> data, then you can stick
> quite happily with punched cards. Some of us need
> more flexibility than
> that.
>
> Don't forget that XML came from the world of
> documents, and was subsequently
> adopted by people who recognized that it was also a
> good way of handling
> complex data.
>
> Michael Kay
> http://www.saxonica.com/
>
>
>
|