Re: C++ COM STA model
George <George@discussions.microsoft.com> wrote:
b) the thread spends most of its time waiting for outgoing
cross-apartment COM calls to return; such calls spin their own
message pumps, or
Do you mean some apartment will call other apartment, and not being
called by other apartment?
Yes.
What means "spin their own message pumps"?
Run a loop calling GetMessage and DispatchMessage.
c) the thread displays a modal dialog box, or uses some other Windows
API that internally runs a message pump.
Can COM runtime share the same message queue with the real UI message
queue?
It can, and often does. There's nothing special about window messages
that COM uses for marshalling.
Do you mean each process could have only one message queue so that
they have to share?
There's one message queue per thread, not per process.
If your interface is not automation compatible, you have to build and
register proxy/stub DLL for it. If it is automation compatible, you
may still choose to build proxy/stub DLL, or you can build and
register a type library for it. COM provides so-called universal
marshaller which can marshal any automation-compatible interface
based on its description in the TLB.
Can you give me some official definition about what is
Automation-compatible types please?
http://msdn2.microsoft.com/en-us/library/ms686605.aspx
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925