INFO: Do Not Store STA Objects in Session or Application

• Active Server Pages, included with:
  • Microsoft Internet Information Server versions 3.0, 4.0

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:

Q175167 HOWTO: Persist Values Without Session

REFERENCES

For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:

Q175167 HOWTO: Persist Values Without Session

Q243544 INFO: Component Threading Model Summary Under ASP

Q243548 INFO: Design Guidelines for VB Components Under ASP

Additional query words:

Keywords : kbASP kbASPObj kbCOMt kbThread kbGrpASP kbScalability kbDSupport
Version : winnt:3.0,4.0
Platform : winnt
Issue type : kbinfo