Re: Saxon for windows?

> > More than inefficient, it would be dangerous to run an XSLT processor as
> part of a *generally available* web service (I can only smile envisioning
> the kinds of creative DOS attacks that would be possible).
>
> Please explain how that would happen when the input is being validated?

  In the general case and endless recursion in the xslt transformation
is impossible to predict. Of course something as simple as :

     <xsl:apply-templates select="."/>

will suffice.


> > When Saxon.NET is released it will accept as input the  .NET System.XML
> XMLDocument, XPathDocument,... etc. and again will be able to produce as
> output native .NET objects, which is  the main fact justifying the ".NET"
in
> its name. Better than this will be only an XSLT 2.0 processor written in
and
> for the .NET platform (e.g. written in C#).
>
> When will that be?


Hopefully very soon -- this question has to be answered by the developer.


Cheers,
Dimitre Novatchev