Re: in-process server considerations

From:

"Alexander Nickolov" <agnickolov@mvps.org>

Newsgroups:

microsoft.public.vc.language

Date:

Fri, 11 Apr 2008 11:47:05 -0700

Message-ID:

<eXRJxRAnIHA.2396@TK2MSFTNGP02.phx.gbl>

I see you've graduated C++ and moved into COM. Please do be
aware that COM is generally OOT (out of topic) here.

The COM newsgroup is:

microsoft.public.win32.programmer.ole

And the group for ATL (a library used for implementing COM) is:

microsoft.public.vc.atl

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================

"George" <George@discussions.microsoft.com> wrote in message
news:01F176FC-AD19-4791-91C8-667D0B23EE29@microsoft.com...

Hello everyone,

Here is the comments from the book ATL Internals about in-process server
considerations,

--------------------
Any thread that calls CoGetClassObject or CoCreateInstance must already
have
joined an apartment, or the call will fail immediately. So, does that mean
all objects exposed from in-process servers must be equally at home in
single-threaded and multithreaded apartments so that random clients isn't
cause harm? Fortunately, no.
--------------------

Does it mean COM client (thread) and COM server no need to be the same
type
of thread model (e.g. STA, MTA, etc.)?

thanks in advance,
George