Kelvin Chung wrote:

Nikolai V. Chr. wrote:

Our application is highly multithreaded, and we manipulate the
scenegraph from several threads at once. If there is a guideline on how
to use Java3D 1.3 in a threadsafe manner, PLEASE tell us Java3D team!!
Since the javadoc mentions nothing of the sort, which normally is an
indicator that everything is threadsafe. Do we need to synchronize on a
global scenegraph lock?? (I hope not)

I really need some feedback from the Java3D team on the multithreading
isssue.

Scenegraph modification has to done in a thread safe manner.
It is especially true if you attach/detach a scene graph or make
a scene graph live.

Please define threadsafe manner?

E.g. which of these operations is not safe:

1) Adding 2 separate branches at the same time to a live scenegraph at
nodes in the graph which are also in seperate branches.
2) Adding 2 separate branches at the same time to a live scenegraph at
nodes in the graph which are in the same branch.
3) Adding 2 separate branches at the same time to a live scenegraph at
the same live node.
4) Adding a branch to a node at the same time the branch which this node
is attached to is being set live.

How is synchronization needed in each of the above cases? E.g. is it
enough in case 3 to synchronize on the node which the two branches are
being added to? Do we have to synchronize on nodes, can we make our own
synchronization object to synchronize on, will it give the same result?
Are the nodes already used for synchronization internally from Java3D
threads?

I hope the Java3D team can help.

thanks
Nikolai

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to