Putting XML in the fast lane

TalkBack 4 of 13:

Next »

« Previous

• Thread View
• Flat View

not enough

Compressing internet traffic is already a common approach. Decompression time vs transfer time is no contest. Modern CPU's can decompress in the blink of an eye compared to transfer rates. The solution is not in simple compression.

One problem is that each time you have a "name" in XML you have a tag . The tag is required for us mortals but redundant to the computer. Compare this to a simple table. For each data type, you only have one "tag" or label for any number of elements. You need a header that contains field widths and data types and the rest is just pure data - not so with XML. However, since XML is a tree structure, there is more than one way to convert it to remove the redundant tags. A java type byte code for XML would be one approach.

Images are yet another problem. One might propose that XML only contain links to images but that would require that the image exist somewhere on a server. If you encode the binary image into text, compress it, uncompress it, decode it, I'm not sure if you'll save bandwidth or time.

Posted by: gsbtech   Posted on: 01/13/05 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• Reducing Server Total Cost of Ownership with VMware Virtualization Software VMware VMware virtualization enables customers to reduce their server TCO and ... Download Now
• Why Isn't Server Virtualization Saving Us More? A Few Small Changes May Dramatically Increase Your Efficiency VMware Companies have rapidly adopted server virtualization over the past few ... Download Now
• Five Steps to Determine When to Virtualize YourServers VMware Server virtualization isn't just for big companies. Entry-level ... Download Now