<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title>Articles by Jimmy Zhang</title>
<link>http://websphere.sys-con.com/</link>
<description>Latest articles from Jimmy Zhang</description>
<copyright>Copyright 2008 WEBSPHERE JOURNAL</copyright>
<lastBuildDate>Sat, 19 Jul 2008 11:22:00 GMT</lastBuildDate>
<generator>WEBSPHERE JOURNAL</generator>
<ttl>10</ttl>
<docs>http://backend.userland.com/rss</docs>

<item>
<title>Index XML Documents with VTD-XML</title>
<guid isPermaLink="true">http://websphere.sys-con.com/read/453082.htm</guid><link>http://websphere.sys-con.com/read/453082.htm</link>
<pubDate>Wed, 20 Feb 2008 14:15:00 GMT</pubDate>
<description>Traditionally DOM or SAX-based enterprise applications have to repeat CPU-intensive XML parsing when accessing the same documents multiple times. VTD-XML 2.0 introduces a simple general-purpose XML index called VTD+XML (http://vtd-xml.sourceforge.net/persistence.html) that eliminates the need for repetitive parsing of those applications.</description>

</item><item>
<title>i-Technology Viewpoint: The Performance Woe of Binary XML</title>
<guid isPermaLink="true">http://websphere.sys-con.com/read/250512.htm</guid><link>http://websphere.sys-con.com/read/250512.htm</link>
<pubDate>Thu, 31 Aug 2006 19:15:00 GMT</pubDate>
<description>Since its inception, XML has been criticized for the overhead it introduces into the enterprise infrastructure. Business data encoded in XML takes five to 10 times more bandwidth to transmit in the network and proportionally more disk space to store.</description>

</item><item>
<title>Process SOAP with VTD-XML</title>
<guid isPermaLink="true">http://websphere.sys-con.com/read/48764.htm</guid><link>http://websphere.sys-con.com/read/48764.htm</link>
<pubDate>Fri, 18 Mar 2005 00:00:00 GMT</pubDate>
<description>SOAP is an XML based data protocol standardized by W3C for the purpose of enabling inter-application data exchange over the Internet. In a typical Web Services scenario, a SOAP message delivered via HTTP needs to be parsed before anything else can happen. As two popular SOAP processing methods, DOM and SAX/Pull force application developers to choose between performance/memory efficiency and ease of use.</description>

</item></channel></rss>