This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: XSLT vs Omnimark
- To: "'xsl-list at mulberrytech dot com'" <xsl-list at mulberrytech dot com>
- Subject: RE: XSLT vs Omnimark
- From: Kay Michael <Michael dot Kay at icl dot com>
- Date: Tue, 7 Mar 2000 10:23:45 -0000
- Reply-To: xsl-list at mulberrytech dot com
> Yes, but how do you get around the fundamental
> requirement for a lot of RAM?
>
> I don't see how we can ever expect to parse a 150meg
> document using XSLT ...
I think it's feasible in principle if the document has a DTD: it should be
possible to create sub-trees of the source document "just-in-time" and to
discard them from memory when they are no longer needed.
Alternatively, it should be possible to create the trees as persistent
objects in an ODB and translate the XPath expressions into OQL queries. All
good stuff for a research project.
But neither of these approaches will ever be as fast as a serial
transformation. To achieve that, I think a different language is needed.
Mike Kay
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list