Cart
[Home] [By Thread] [By Date] [Recent Entries]
<cut> Discussion about a weaker version of XSL where sequential access is a sufficient condition for processing and random access is not the necessary condition. </cut> Michael.Kay@i... wrote: > > How do I build a table of contents that is output BEFORE the document > > without reading the whole input before I start to output? > > You can't, and that isn't my objective. What you can do, and what I > currently do with SAXON, is to perform a single serial pass of the input > document that simultaneously generates a TOC and the main rendered document > on two separate output streams, then merge these together for presentation. > This is far more efficient with a large document than building the entire > document tree in memory or scanning it twice. Stream processing! This is what I initially assumed XSL did. It's so nice to hear that I'm not on another planet. It's about time we considered the case when an XML document is a sequentially accessed stream. Wonderful! Michael, how do I get SAXON? I'm excited. :) Clark -- flyweight n : 1. the most confusing part of the otherwise wonderful Design Patterns book 2. when everything looks like a nail xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1 To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
