RE: LINQ to XML versus XSLT

> From: James A. Robinson [mailto:jim.robinson@xxxxxxxxxxxx]
> Sent: Friday, June 27, 2008 3:31 PM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re:  LINQ to XML versus XSLT
>
> Consider the scenerio where you have five different stylesheets,
> each operating on a representation of the incoming HTTP request, each
> responsible for collecting data from some service point and combining
> it all into an aggregate document.
>
> Controlling whether one template execution should take priority over
> others, or controlling whether one template may be executed but does
> not need to finish before the final result document is constructed are
> not currently possible (at least as far as I know).
>
> You might wonder why we would want to crafting a system where one
> template may or may not complete before we send out the final page.
> The answer is that some services might take awhile to respond, and if
> we've finished the rest of the page before that response comes back,
> we might want to simply annotate the outgoing page with an AJAX
> callback
> which will fetch the final result at some later point in time.
>
> XSLT doesn't currently give that kind of fine grained control.

No XSLT doesn't give you that control, but you have given a scenario where
there are other environmental factors which could be handled by things like
load balancing and/or tools like Apache Synapse or Xproc that allow you to
call XSLT or XQuery from a pipeline of processing steps.


Andy.