This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: XSLT vs Omnimark


James Robertson wrote:

> 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 ...
> 
> But for all the small, everyday documents, I absolutely
> agree with you.

Unfortunately, my small, everyday documents are several megs each
(microprocessor specs are not known for their brevity). What we need is
a "lazy" implementation of XSLT that only builds as much of the tree as
it needs to process a given document with a given stylesheet. Are any of
the current implementations working this way?

Rick Geimer
National Semiconductor
rick.geimer@nsc.com


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]