Java 3D protects its internal accesses from user set methods. We will
never read a partially copied matrix, so you can set a transform from
any thread without worrying about synchronizing with the Java 3D
renderer.
Note that we don't protect the case where two user threads call set or
one user thread calls set while another user thread calls get. These
would not be not thread-safe.
--
Kevin Rushforth
Java 3D Team
Sun Microsystems
[EMAIL PROTECTED]
>Date: Mon, 9 Apr 2001 22:29:10 +0200
>From: Artur Biesiadowski <[EMAIL PROTECTED]>
>
>Justin Couch wrote:
>> Even if the TG changes, the view platform's matrix does not
>> so you never end up with any odd shearing effects.
>
>I'm not worried about TG being accessed two times with different values.
>I worry about case where matrix data is copied value by value and
>preemptiveness kick in during that - half of matrix is updated and half
>not. Matrix can be very wrong then - you know, all 0, constant etc.
===========================================================================
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".
