JavaPartyA distributed companion to Java
Current release 1.9.5
Bernhard Haumacher, Thomas Moschny and Michael Philippsen
Because the regular Java class java.lang.Thread is
non-remote, it can only be allocated on the current node. To make
allocation of activities on remote nodes more convenient, JavaParty
declares a simple wrapper class for remote threads. The class
Figure 1 shows the situation, where the application creates a new
Figure 1. Using
The invocation of the
There is another possibility to create activities on far nodes,
without using the
Figure 2. Using a local thread to create activities on remote nodes.
When starting the local Java thread, it immediately performs a
remote method invocation to the
With JavaParty's Transparent Threads, both approaches are functionally equivalent. The first one might consume slightly less resources, because there exist one activity less than in the second approach. The second one is slightly more convenient, because starting the activity is indistinguishable from regular Java.
For comments and bug reports please use the JavaParty users mailing list.
Page design & maintenance: Bernhard Haumacher.
Last update: Fri Mar 30 18:46:00 GMT+01:00 2007
Java is a trademark of Sun Microsystems.