xsl-list
[Top] [All Lists]

Re: [xsl] xslt architecture

2008-05-22 02:44:33
I think the question of which processor is involved also can add in
some overhead. For example I seem to remember that MSXML used to open
everything as a new DOM. This however was quite a while ago so not
sure if it has been changed since.

Cheers,
Bryan Rasmussen

On Thu, May 22, 2008 at 11:24 AM, Andrew Welch 
<andrew(_dot_)j(_dot_)welch(_at_)gmail(_dot_)com> wrote:
From a processor's perspective: is there any difference between one
stylesheet containing 100 templates and 100 stylesheets each
containing 1 template each, with an extra stylesheet containing 100
include statements?

Import precedence issues aside, if they were 100 imports instead of
includes, does that make a significant difference to the processor?
(all unique files imported once, not the same file imported in
multiple locations)

I tend towards monolith stylesheets where there's usually no more than
a dozen or so large stylesheets, but in front of me now is the
complete opposite approach and I'm not keen...

--
Andrew Welch
http://andrewjwelch.com
Kernow: http://kernowforsaxon.sf.net/

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--



--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--

<Prev in Thread] Current Thread [Next in Thread>