Hi Anders,

On 2/17/07, Anders Backman <[EMAIL PROTECTED]> wrote:
Its only good news to have fewer dependencies.
The question is, how many is using OpenTHreads without OpenSceneGraph?

I my last exchange Sean says that are few people in the HPC world
using OpenThreads.

As far as I'm aware all the contributions to OpenThreads over the
years have been from the OpenSceneGraph community so I don't know how
much they are pushing OpenThreads, or whether its still being actively
used.

So non OpenSeneGraph OpenThreads using please raise your hands :-)

I mean there are boost::threads also? (and a zillion other thread toolkits).

Sean also mentioned the possibility of migration to another thread
toolkit such as Intels.  This is something we might even want to
consider for the OpenSceneGraph in the longer term.  Not for now
though, we need to evolve the project rather than make too many
radical changes at once.

I have a class that I wanted to add to OpenThreads. I got ok several months
ago, but nothing has happened...
So perhaps I can email you the stuff instead Robert so you can review them
for inclusion into OpenThreads?
I would like to lift that class outside of osgHaptics.

I recall the dicussion and you getting the thumbs up, but I don't ever
recall a submission.  Did you send it Sean directly or to
osg-submissions?

Just re-submit them.

The changes for Qt threads also disappeared into the ether so this is
something else that it'd be nice to resurrect.

Also, the osgDB::reentrentMutex is another class that should go into
OpenThreads, right? Its really better suited for OpenThreads than osgDB.

Yes ReentrantMutex and the new ReadWriterMutex should go into OpenThreads.

Migrating the ReentrantMutex to a more efficient implementation would
also be useful.  I also have come across some issues with it in
certain types of usages, but haven't been able to track down the exact
circumstances.

I really like to use that kind of Mutex to avoid locks in the api. Costs
more but lets you think of the api instead of what methods that can call
eachoter..

Cost is a big factor for commonly used methods.  But for high level
stuff, and implementing certain algorithms the ReentrantMutex is
essential.

Robert.

Robert.
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/

Reply via email to