xquery & web server in browser

[Robert Koberg]

On Jun 18, 2009, at 8:23 PM, Florent Georges wrote:

>
> John Snelson wrote:
>
>> The problem is the dynamic dispatch in XSLT - you can't
>> know at compile time which template will be invoked where.
>> This is a problem because:
>
>> 1) You generally can't get accurate static type information
>> across template application.
>> 2) You generally can't optimize across template application
>> boundaries.
>
>> I think these aren't necessarily as much of an issue has
>> they have traditionally been thought as.
>
>  Yes.  My guess is that this could become a problem as third-party  
> XSLT libraries will become to be more and more used.  Even if such a  
> library is installed once, it couldn't be compiled once at the  
> global level.  It should be compiled once for each stylesheet using  
> it,

But, I think the point is (and the beauty of XSL) you can't know the  
templates applied based on the XSL, rather it would be based on the  
source XML, and the source xml can vary. An XSL can behave radically  
different based on the source XML being fed to it.

-Rob


> unless some assumptions can be verified.
>
>  Maybe XSLT 2.1 will provide some way to handle that problem.  But  
> as you said, this is not clear that's something useful.  Wait and  
> (maybe) see...
>
>  Regarding dynamism of a query, first-class function items will be  
> very interesting.  That's not the same thing as being able to  
> overload a template rule, but that will provide a module the ability  
> to change the behavior of an imported module (in some explicitly  
> defined ways though.)
>
>  Regards,
>
> -- 
> Florent Georges
> http://www.fgeorges.org/
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>