John,
>This brings up something I do not understand. Take a single use exe com server in a pool for the web. It's protected from any other hit? For instance a cReturnHTML property is safe cause the server is single use? But you can have 2 or more instances going.
Yep. Each EXE's properties and methods are independent of each other with Single-Use.
>What about a multithreaded dll com server doing the same, say with ASP? Its init and destroy are initialized with each request but a property like cReturnHTML can be trampled? I'm trying to picture what is instantiated and what is separated or shared and don't get it. Thanks
Your multithreaded dll's will be built as Single-Use and run inside MTS, which handles runtime management and object instantiation for multiple requests. The multithreaded runtime allows for "thread local storage", which can keep memory for different "hits" separated.
The MTS article by Randy Brown, and also the article by Rick Strahl, may help you get the picture. Look particularly at the parts dealing with Just-In-Time Activation.
http://msdn.microsoft.com/library/default.asp?URL=/library/techart/MTSVFP.htmhttp://www.west-wind.com/presentations/mts/mts.htm
