Hi Kevin !
Thanks for your reply.
>
> >I thought that all Behaviors are executed in the same thread ?
>
> It does today, but that could change in the future. Btw, when I said
> "AWT event behavior", I really meant "AWT event listener callback
> method" (i.e., a method called by the AWT or Swing event thread).
In case that there will be more than one thread for Behaviors:
Is it then the duty of the application programmer to avoid that two Behaviors change
the same object e.g. TransformGroup at the same time or is it duty of the
implementation of the Java3D Behavior handling ?
> >I would appreciate some documentation about the Java3D thread Model. Thanks.
>
> As Justin indicated, we have been reluctant to do that. This is
> primarily because we don't want to specify the threading behavior too
> tightly--it could change in a future release. We do realize that we
> need to document the minimum set of rules so that an app can do the
> right thing.
I understand that you do not want to limit the Java3D implementation with to tight
specification. I would say, something similar like the performance guide would be
very helpful.
regards
Paul
===========================================================================
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".