Re: Pipelined XSL
| From: | Christian Stocker | Date: | Wed, 12 Mar 2003 21:30:05 +0000 |
| Subject: | Re: Pipelined XSL | ||
| References: | 1 | Groups: | php.xml.dev |
| Request: | Send a blank email to php-xml-dev+get-46@lists.php.net to get a copy of this message | ||
On Wed, 2003-03-12 at 22:01, Alexandru COSTIN wrote:
> Hello guys,
> I know I've heard Sterling saying something about pipelined XSL
> transformations, and we would like to know if anything is planned for the
> XML support in PHP 5 (I think he refered the napa XSL project, which is
> pretty dead).
I'm not sure, what exactly you mean with "pipelined XSL
transformations". I assume, it's not:
DomDocument -Transformation-> DomDocument -XSLT-Transformation-> (
...etc..) -> EndResult
or is it more sth like:
http://xml.apache.org/xalan-j/usagepatterns.html#outasin
> We are running in some memory problems with huge XML trees and I wonder
> if they could be corrected using some kind of input/output streams.
libxslt needs the whole document in the memory before processing. I'm
not sure, if there are XSLT-Processors out there, which can handle that
differently. Even Xalan has to read the whole Document (but not
necesseraly the whole thing at once into the memory, see
http://xml.apache.org/xalan-j/design/design2_0_0.html#stree
dor some
detilas)
> Is there any method of compressing the size of XML trees in memory
> (there is a compression attribute which is always -1 as far as I recall).
Attributes in the current DomXML are sth not worth looking at and not
really used internally (some leftovers from early developement). But I
think, the compression attribute was intented to use for compressing the
serialized XML Document. Compressing the tree in memory? Mmmh, would
definitively slow down performance and is IMHO not very practical.
chregu