| 1 |
The standard Jini mechanism is applied for each chosen embryo. This effectively establishes an RMI link from Gateway to (SPMD) node which corresponds to creating a Java proxy (corresponding to RMI stub) for the node program which can be any language (Java, Fortran, C++ etc.)
|
| 2 |
This Gateway--Embryo exchange should also supply to the Gateway any needed data (such as specification of needed parameters and how to input them) for user client layer
|
| 3 |
This strategy separates control and data transfer
-
It supports Jini (registration, lookup and invocation) and advanced services such as load balancing and fault tolerance on control layer
-
and MPI style data messages on fast transport layer
-
The Jini embryo is only used to initiate process. It is not involved in the actual "execution" phase
|
| 4 |
One could build a JavaSpace at the Control layer as the basis of a powerful management environment
-
This is very different from using Linda (JavaSpaces) in execution layer as in Control layer one represents each executing node program by a proxy and normal performance problems with Linda are irrelevant
|
