CComSingleThread is only choice for COM DLL and not for COM SERVER ideally.
Thanks,
Krushna
----- Original Message -----
From: "Stephan Deckers" <stephan.deckersMOLDING.FICO.NL>
To: <DCOMDISCUSS.MICROSOFT.COM>
Sent: Thursday, January 16, 2003 1:58 PM
Subject: CComSingleThreadModel vs. CComMultiThreadModel

> As I understand COM, A COM-client should not be bothered
> whether a server is multithreaded or not. If the clients
> chooses to use a COM-object in more then one thread, access
> to the object properties should be thread safe and handled
> by the server. Thread-safe implementation of properties is
> a task of the developer, but the ATL-wizard is responsible
> for thread-safe reference-counting. If a Server is to be
> used in a multithreaded environment, CComMultiThreadModel
> should be chosen as the threadingmodel.
>
> In this respect I don't understand why the CComSingleThread
> is even a choice, since you never know what a clients threading
> model is.
>
> thanks for any input, Stephan
>
> ----------------------------------------------------------------
> 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 ]