ActiveX: MTS implementation needed or not.

[Guest_imported]

Hi,
I want to create an ActiveX DLL that will be implemented on an ASP page and will be stored in a session object. This ActiveX will store information and write it to a DB when needed. the question is: do I need to create it as an MTS package or can I just create it as a normal ActiveX DLL?

Thank you.

 

[slanford]

If you are going to store the object in a Session variable then you definitely do no want to implement it in MTS. There is probably no harm in doing it but certainly no benefit either. Storing an MTS object in a Session variable is bad practice because it forces thread affinity on the object thereby negating any scalability benefit you might recieve from MTS. Besides, if the component is not written to take advantage of MTS (i.e. SetComplete(), etc.) then you really would not get any benefit from MTS anyway.
If scalability is a a concern then you may want redesign your component for MTS using MTS best practices, being sure to not store the object in a Session variable and create/destroy it as needed.
If scalability is not a concern then just implement your component as a normal ActiveX DLL.

Hope this helps,
Scott