VTD-XML is a next generation XML processing model that is very memory efficient, fast, and capable of handling large XML documents. It uses virtual token descriptors to non-destructively parse XML into memory. Typical programming with VTD-XML involves parsing an XML file, moving a cursor through the document structure using XPath queries, and performing operations to modify or extract data from the XML. The demo shows examples like adding, removing, and traversing nodes in an XML document.

1. VTD-XML: The Future of XML ProcessingAlbert Guojunyuo@gmail.com

2. VTD-XMLMotivations Behind VTD-XMLWhy VTD-XML?When to Use VTD-XML?Known LimitationsBasic ConceptEssential ClassesShortcomingsTypical Programming FlowsDemoReferenceAgenda2

3. *Numerous*, well-known issues of old XML processing models, below summarizes a few:Comparison with DOM, SAX and PULL http://vtd-xml.sourceforge.net/userGuide/5.htmlMotivations Behind VTD-XML3

4. The next generation XML processing model that is simultaneously:

5. The world's most memory-efficient random-access XML parser.

6. The world's fastest XML parser

7. The world's fastest XPath 1.0 implementation.

8. The world's most efficient XML indexer that seamlessly integrates with your XML applications.

9. The world's only incremental-update capable XML parser capable of cutting, pasting, splitting and assembling XML documents with max efficiency.

10. The world's only XML parser that allows you to use XPath to process 256 GB XML documents.Why VTD-XML?4

11. The scenarios that you may consider using VTD-XMLLarge XML files that DOM can’t handlePerformance-critical transactional Web- Services/SOA applicationsNative XML database applicationsNetwork-based XML content switching/routing/security applicationsWhen to Use VTD-XML?5

12. Not yet support external entities (those declared within DTD)

13. Not yet process DTD (return as a single VTD record)

14. Schema validation feature is planned for a future release.

15. Extreme long (>=512 chars) element/attribute names or ultra deep document (>= 255 levels) will cause parse exception

16. http://vtd-xml.sourceforge.net/userGuide/0.htmlKnown Limitations6

17. Basic ConceptNon-extractive tokenization based on Virtual Token Descriptor (VTD): use 64-bit integers to encode offsets, lengths, token types, depths

18. The XML document is kept intact and un-decoded.7

19. Basic Concept – cont.In other words, in vast majority of the cases string allocation is *unnecessary*, and nothing but a waste of CPU and memory

20. VTD-XML performs many string operations directly on VTD records

21. String to VTD record comparison (both boolean and lexicographically)

22. Direct conversions from VTD records to ints, longs, floats and doubles

23. VTD record to String conversion also provided, but avoid them whenever possible for performance reasons8

24. Basic Concept – cont.VTD-XML’s document hierarchy consists *exclusively* of elements

25. Move a single, global cursor to different locations in the document tree

26. Many VTDNav’s methods identify a VTD record with its index value