Here is another link.
>From memory it is preferable that COM objects for best performance under ASP that
>they are Free-Threaded.
Single Threaded apartments work, but ASP has to marshal the calls from the
multi-threaded apartment to a single threaded apartment (hence the overhead), but it
depends on the expected load.
If objects are required at the session or application level then they have to be
Free-Threaded and they also must aggregate the COM Free Threaded Marshler - easier to
do than understand or do your own marshalling/unmarshalling code - real nasty.
Basically if you use the apartment model = Single threading = then no special code is
required.
Free-Threading=Multi-Threading= Special Thread protection code required = critical
sections, events, mutexs etc.
http://msdn.microsoft.com/msdn-online/workshop/components/com/comthread.asp
-----Original Message-----
From: Neil Anderson [SMTP:[EMAIL PROTECTED]]
Sent: Friday, July 16, 1999 12:32 PM
To: Multiple recipients of list delphi
Subject: [DUG]: ASP and threading models etc
Hi all
I have developed some ASP COM objects using multiple instancing and
apartment model.
Could someone either explain how these options relate to the model ASP
expects or point me to an article/paper which could help me understand this
issue ?
I am also not sure if I have to be careful in the way I code my app
depending on these settings
Thanks Neil
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
application/ms-tnef
