Microsoft KB Archive/243543

= INFO: Do Not Store STA Objects in Session or Application =

Article ID: 243543

Article Last Modified on 9/17/2003

-

APPLIES TO

 Microsoft Active Server Pages 4.0, when used with:  Microsoft Internet Information Server 3.0

 Microsoft Internet Information Server 4.0 

-



This article was previously published under Q243543



SUMMARY
Do not store Single-Threaded Apartment (STA) COM components in an Active Server Pages (ASP) Session or Application.



MORE INFORMATION
Storing objects that are marked as STAs, such as components produced by Visual Basic (ActiveX DLLs), limit scalability and can negatively impact performance. Storing STAs in Session scope causes thread affinity and defeats the purpose of a thread pool. When an STA component is stored in Session scope, all subsequent ASP requests from the same user (session) must be executed by the thread that created the component.

In general, stateless page-scoped components perform best. Page-scoped components are COM objects that you create and destroy within the same ASP page. If you need to pass state information from page to page, the following article demonstrates possible techniques that do not use Session:

175167 HOWTO: Persist Values Without Session

