Re: [xslt] Re: [xml] Iterating through multiple HTML docs



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

At 04:14 1/4/02, Daniel Veillard wrote:
>   Okay, 2 things:
>     - delaying the serialization of <xsl:document> result may not be
>       a good idea in all cases, it ends up consuming more memory for
>       a longuer time

True.  There probably ought to be an option... immediate serialization 
means that relative URIs may have unexpected behavior, and that the result 
trees are unavailable, but deferred serialization means that memory is 
consumed.

>     - how to provide access to the not yet serialized document tree
>       from the API. It seems the best is to associate them with the
>       transformation context and provide an iterator the structures
>       could be identical to the ones already used for caching docs
>       coming from document(). The other API addition needed would be
>       a way to toggle bewteen the existing and delayed behaviour.
>       Freeing the transofrmation context would then free the
>       document list.

That sounds spot-on.

I wonder where the XSL WG is heading on this issue.  If xsl:document is to 
be part of XSLT 2.0 (which is my understanding), then the data model ought 
to be better-defined.  Unfortunately, it seems like Query "harmonization" 
is stealing all their cycles, and extremely useful issues like this are 
getting buried.

~Chris
- -- 
Christopher R. Maden, Principal Consultant, crism consulting
DTDs/schemas - conversion - ebooks - publishing - Web - B2B - training
<URL: http://crism.maden.org/consulting/ >
PGP Fingerprint: BBA6 4085 DED0 E176 D6D4  5DFC AC52 F825 AFEC 58DA
-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.5.8

iQA/AwUBPKhQyqxS+CWv7FjaEQJ5UwCg3/qUtLkGrUu/RzoeoaMu1tnpYNoAoMQx
Kra9Ovl4UiyICkx9cxHaBwD8
=BG18
-----END PGP SIGNATURE-----




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]