[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Co-operating with Architectural Forms

• To: "'michael.h.kay@n...'" <michael.h.kay@n...>, xml-dev@l...
• Subject: RE: Co-operating with Architectural Forms
• From: Michael Brennan <Michael_Brennan@A...>
• Date: Mon, 4 Feb 2002 15:01:05 -0800

> From: Michael Kay [mailto:michael.h.kay@n...]

<snip/>

> I think the number of cases where you can do this 
> automatically is rather limited, though it might become 
> rather more feasible if the optimizer has knowledge of the 
> schema. It only takes a single template that uses "..", or a 
> leading "//", or <xsl:number/>, or key(), or various other 
> things, to make the optimization invalid, unless you know for 
> certain that these are only selecting within the current subtree.

What if you avoid such constructs? What if all your expressions only select
along the child and attribute axes -- are existing XSLT engines (SAXON, for
instance) smart enough to optimize for that and not try to hold the entire
document structure in memory?
 

• Follow-Ups:
  • RE: Co-operating with Architectural Forms
    • From: "Michael Kay" <michael.h.kay@n...>

• Prev by Date: RE: Categories of Web Service messages: data-oriented vs action-oriented
• Next by Date: RE: looking for XML vendor in Santa Clara
• Previous by thread: RE: Co-operating with Architectural Forms
• Next by thread: RE: Co-operating with Architectural Forms
• Index(es):
  • Date
  • Thread