It means that you skipped or don't understand the discussion in the sibling thread (wrt thread safety in reality, not nominally and incorrectly). You won't be able to logically explain how it could become thread safe when it comes to XslCompiledTransform.
For reference, we don't have true XslCompiledTransform. It's just a wrapper of XslTransform. Atsushi Eno Steve Bjorg wrote: > Hmm, except the docs for XsltCompiledTransform explicitly states that > the object is thread-safe once loaded. > >> Thread Safety >> The XslCompiledTransform object is thread safe once it has been >> loaded. In other words, after the Load method has successfully >> completed, the Transform method can be called simultaneously from >> multiple threads. > > > Frankly, loading the XSLT per thread is not an option for us either. > Hence why we used the XsltCompiledTransform class. > > - Steve > > -------------- > Steve G. Bjorg > http://wiki.mindtouch.com > http://twitter.com/bjorg > > On Jul 17, 2008, at 7:49 AM, Joshua Tauberer wrote: > >> Steve Bjorg wrote: >>> XSLTCompiledTransform is thread-safe. Would that be an alternative >>> for you? >> >> As far as I know, XSLTCompiledTransform (in Mono) just wraps the same >> code as XslTransformation, so they are equally thread safe. >> >> The MSDN docs seem to basically say the same thing w.r.t. thread >> safety, as well (and not mentioning scripts and extension functions). >> >> -- >> - Josh Tauberer >> >> http://razor.occams.info >> >> "Yields falsehood when preceded by its quotation! Yields >> falsehood when preceded by its quotation!" Achilles to >> Tortoise (in "Godel, Escher, Bach" by Douglas Hofstadter) > > _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
