notify on the MasterControl thread. The other arguments
notify on the MasterControl thread. The other arguments are (in order): the array of State Work Threads, the array of Render Work Threads, and the array of Request Render Work Threads. As you can see in the following pseudocode, Java 3D has the ability to call the doWorkmethod on each worker thread directly. This enables Java 3D to perform the work of multiple threads within a single thread. For all Render Work Threads If the Thread needs to be run (J3dThreadData member), Check whether the View should be rendered based on its Minimum Frame Cycle Time Update the OrientatedShape3Ds in each View If specified lock the geometry from updates, If the CPU limit is 1, call the doWork method of the J3dThreadData s J3dThread directly Otherwise call the runMonitor method (NOTIFY) to notify the thread If specified release the lock on the geometry, If specified, grab the current time and put it into the View s RenderBin Next Rendering Thread If specified, wait for all Rendering threads to complete For all State Work Threads If the CPU limit is 1, call the doWork method of the J3dThreadData s J3dThread directly Otherwise call the runMonitor method (NOTIFY) to notify the thread Next State Thread If specified, wait for all State threads to complete For all Request Render Work Threads If the CPU limit is 1, call the doWork method of the J3dThreadData s J3dThread directly Otherwise call the runMonitor method (NOTIFY) to notify the thread Next State Thread If specified, wait for all State threads to complete Update the View Frame Timing Values Update all the Mirror Objects registered with the MasterControl Wait for Request Rendering to complete Update the frame timestamps for each rendered View J3dMessage Java 3D communicates between its various worker threads using a message dispatch mechanism. Messages are instances of the J3dMessageclass. Each message contains an identifier and a target VirtualUniverseas well as up to five parameters for the message (generic Objects). Certainly not the most OO of designs in fact it reminds me of the WPARAM and LPARAM attributes on the MESSAGE structure used to propagate messages under Windows. The message identifiers are defined in table 18.5. Table 18.5 Message identifiers Message Identifier INSERT_NODES 0 318
Check Tomcat Web Hosting services for best quality webspace to host your web application.