RE: [xslt] Thread safe?



> 
> Thanks for your answer Mark. But how do you do to
> report the errors (and eventually the debugging
> output) for different instanciations of the COM object
> given that they are forced to use the same context
> (xmlGenericErrorContext)?

In my case not really a problem.  The COM object is apartment threaded, with
only 1 instance of the COM object existing in the same process at any given
time.  I could see how you would run into problems with free-threaded COM
objects.

In my case when you navigate to the uri in Internet Explorer
xslt://SA/?src=zip://xml.zip/xml/source.xml&stylesheet=zip://xml.zip/xslt/st
yle.xsl the result of the transform is displayed in the browser.  (zip:// is
an libxml2 input callback that extracts the files from a .ZIP archive, sort
of like catalogs I suppose).  Only one instance of the asynchronous
pluggable protocol is instantiated, and in my case the program hosting the
IE control maintains only 1 instance of IE per process.




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]