[omniORB] Single Threaded Policy: really same thread?

[Kevin Wooten]

Sorry, the tone of my reply was a bit more than I wanted. I am forced to
use COM and all its crazy threading models, so I am a little bit jaded.

> -----Original Message-----
> From: JHJE (Jan Holst Jensen) [mailto:jhje@novonordisk.com]
> Sent: Wednesday, December 18, 2002 3:26 AM
> To: Kevin Wooten; omniorb-list@omniorb-support.com
> Subject: RE: [omniORB] Single Threaded Policy: really same thread?
> 
> > apartment. This is required to preserver apartment contexts. Look
into
> > the reason for the threading style "both", which allows
> > single threaded
> > apartments to create components as single threaded and multi
threaded
> > apartments to create them multi threaded, but it does not stop the
> > thread switches.
> 
> OK, thanks for clearing this up. But if object A and B are both
> free-threaded surely there is no thread switching when A calls B ? Or
did
> I
> miss something (may easily happen when talking about COM threading :-)
) ?
> 

Correct.

> > IMHO, people who "don't have to think about thread safety" should
not
> > really be using multiple threads. It is to dangerous and
> > confusing of a
> > topic that most experienced programmers don't fully understand, and
> > trying to make it "easy" for them is somewhat crazy.
> 
> I completely agree, but when people use third-party components they
may
> use
> multi-threaded components without knowing it. So protection against
> multi-threading issues is per se a good thing.
> 

This is a view I did not think of, since most of our controls are used
by us alone.

> > Not only is the concept confusing, it is slowing everything
> > down! To me
> > this is ludicrous!
> 
> Yeah. Should have been done otherwise, and if you could only switch it
> off...
> 
> -- Jan