Cart
[Home] [By Thread] [By Date] [Recent Entries]
It's in tracking the dependencies that I see the problems.
If it can be mapped out, I don't think it's infeasible. And we know about micropipelining in XSLT2 -- (I've even done it). What concerns me would be tangling up what is supposed to happen when (or maybe, what would interest me is how to express and manage the dependencies). Cheers, Wendell At 07:12 PM 8/11/2005, you wrote: Actually, I don't think this is quite so impossible. Given the evaluate() and node-set() extensions, it seems quite feasible to write a recursive process that reads an XPath expression, creates a new tree that modifies the nodes selected by that expression in some way, and then continues by reading the next XPath expression to create another new tree and so on. Whether it's a good application design is another matter, but I don't think it's infeasible. ====================================================================== Wendell Piez mailto:wapiez@xxxxxxxxxxxxxxxx Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================
|
