Re: C++ COM STA model

Thanks Igor,

1.

It makes me recall some C# threading stuff, but more related to COM STA
model. I think "Join keeps message pumping alive while blocked; Sleep
suspends message pumping", I think means Join is better than sleep since
during join a thread's message window could still accept message from other
apartment, but if a thread is sleep, all the messages to the window will be
blocked. It means sleep will block operations from other apartment, right?

http://www.albahari.com/threading/part2.html

--------------------
Joining a Thread
You can block until another thread ends by calling Join:

class JoinDemo {
  static void Main() {
    Thread t = new Thread (delegate() { Console.ReadLine(); });
    t.Start();
    t.Join(); // Wait until thread t finishes
    Console.WriteLine ("Thread t's ReadLine complete!");
  }
}
The Join method also accepts a timeout argument ??? in milliseconds, or as a
TimeSpan, returning false if the Join timed out rather than found the end of
the thread. Join with a timeout functions rather like Sleep ??? in fact the
following two lines of code are almost identical:

Thread.Sleep (1000);
Thread.CurrentThread.Join (1000);
(Their difference is apparent only in single-threaded apartment applications
with COM interoperability, and stems from the subtleties in Windows message
pumping semantics described previously: Join keeps message pumping alive
while blocked; Sleep suspends message pumping).
--------------------

2.


Sorry it is new to me. I want to confirm with you that, COM runtime is
responsible for creating the window, and I am responsible for retrieving
message from message queue, process it, and return message into the queue,
right?

regards,
George