| 1 |
Consider large class of problems that can be thought of a set of coarse grain entities which could be internally data parallel and the coarse grain structure is "functional or task" parallelism
|
| 2 |
Use (Enterprise) JavaBeans to represent modules at (server) client level
|
| 3 |
Use UML (and related technologies) to specify application and system structure
|
| 4 |
WebFlow is graphical (Java Applet) composition palette (Beanbox for computational modules)
|
| 5 |
Use "To be Agreed Seamless Computing Interface" to implement linkage of proxies to backend hardware
|
| 6 |
We can support any given paradigm at either high functionality (web server) or high performance (backend) level
|
| 7 |
HPCC Messaging could be a pure Java/RMI middle tier version of MPI or Nexus/Optimized Machine specific MPI at backend
|
