XML Component API

[Michael.Kay at icl.com]

> > I've recently been trying to implement an XSL subset using SAXON and
have
> > realised that the XSL processing model requires the document to be built
in
> > memory, even though 90% of useful applications don't. For an XSL API,
> > therefore, I think you can forget any idea of an event-based approach.
> >
> > Mike Kay
> 
> That has not been my experience.  I have not had any problem with spitting
out
> processed XSL Output to SAX events.  Things could change, but for now I
have not
> found any reason why you can't use DocumentHandler as an interface for
delegating
> processing of XSL output.
> 
> Tyler
> 
Sorry, I wasn't clear and you misunderstood me. By "the document" I meant
the input document to XSL, not its output. For the output document, yes, you
are right.

Mike

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)