As for protecting data, yes, you must if it's pooled. You should make your
components "stateless".

This usually means small components and more parameters than you'd care, but
in the end it pays for itself in spades.

We have a fairly large COM+ system with about 50 components. The only
non-stateless data we have is data that we "cache" in several components,
for performance reasons. In these cases, the data is usually stored for the
life of the component and thread synchronization is required.

Pete
----- Original Message -----
From: "Charles Gamble" <Charles.GambleSINGULARITY.CO.UK>
To: <DCOMDISCUSS.MICROSOFT.COM>
Sent: Monday, October 01, 2001 12:03 PM
Subject: COM+ and free threading

> Hi all,
>
> I realise that when you setup a COM+ component to be threading model
"Both",
> it uses the STA thread pool provided by COM+ which is restricted to use
8 -
> 10 concurrent threads on a single CPU thread. My question is, if I have a
> component setup to be threading model "Free", will this use the STA
> threadpool? If not, will it be restricted in the number of concurrent
> threads that can access it?
> Also, will the component have to be thread safe, protect instance data,
> etc.? Or will this be provided by COM+?
>
> Any help is appreciated.
> Charles Gamble.
>
> ----------------------------------------------------------------
> Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
> contains important info. Save time, search the archives at
> http://discuss.microsoft.com/archives/index.html .
> To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]