Hi - having read most of what I can find out there on the subject, I still feel unsure of the definitive answer to my question, namely:
I've built a navigation generation module using XML/XSLT. Originally I wanted to parameterise it and so used the xslTemplate object and the FreeThreadedDOMDocument (as required). So far so good. Once I'd finished it in ASP I turned it into a COM+ app for ease of ASP coding/performance reasons. All was well.
Then I read that using free threaded objects in conjunction with IIS was a big no-no from a stability point of view - opinions seem to be divided on whether it's safe to do this sort of transformation in a COM+ object and pass back the HTML as a string to the ASP for display, which is what I ended up doing.
So, after that I went back and developed another version of it that uses no parameters, combining SQL and XSL to deal with all my conditionality and display issues. This also seems to work fine - but just now I've read that my COM+ solution should be safe!
I'm a little frustrated to say the least - does anyone have a definitive answer to this please? There is only a single parameter being passed into the free threaded XSL, and nothing else dynamically altered in that way. Only the parameter value changes.
I'd prefer to sue the parameterised COM+ version, given the frequency with which the navigation is generated, and the ease of use it offers, but stability is paramount.
Many thanks in advance,
Graham
I've built a navigation generation module using XML/XSLT. Originally I wanted to parameterise it and so used the xslTemplate object and the FreeThreadedDOMDocument (as required). So far so good. Once I'd finished it in ASP I turned it into a COM+ app for ease of ASP coding/performance reasons. All was well.
Then I read that using free threaded objects in conjunction with IIS was a big no-no from a stability point of view - opinions seem to be divided on whether it's safe to do this sort of transformation in a COM+ object and pass back the HTML as a string to the ASP for display, which is what I ended up doing.
So, after that I went back and developed another version of it that uses no parameters, combining SQL and XSL to deal with all my conditionality and display issues. This also seems to work fine - but just now I've read that my COM+ solution should be safe!
I'm a little frustrated to say the least - does anyone have a definitive answer to this please? There is only a single parameter being passed into the free threaded XSL, and nothing else dynamically altered in that way. Only the parameter value changes.
I'd prefer to sue the parameterised COM+ version, given the frequency with which the navigation is generated, and the ease of use it offers, but stability is paramount.
Many thanks in advance,
Graham