Paul ([EMAIL PROTECTED]) writes:
>...The user types in some numbers and clicks on a button, which adds
>more data to the source. The transformer is invoked again, but instead
>of regenerating the entire result, it determines which parts of the
>result are dependent on the changed source elements, prunes them, and
>regenerates them (and only them).
>...
>Can you foresee anything that would make it difficult to map the
>dependencies?
It *is* hard to do. Here's one example of why:
<xsl:template match="x/y[a > b]/z[c < 1000]">
where a, b, and c are some numbers that you allow the user to change
on the fly. Thus, the set of z nodes that are processed by this
template varies according to a, b, c values. Embellish this idea with
more templates, etc.
.................David Marston
