Although Javabeans exhibit this model, one needs it throughout the portal and a distributed object system should have some sort of event service and messaging service
-
In fact one will have multiple such services (on clients and different subsets of servers running disparate pragmatic object web services) and they need to be federated together
|
|
The messaging service needs support appropriate queuing and other constraints
|
|
Software is built using Design patterns and other software engineering techniques
|
|
Note modules in Portal Programming are larger (coarse grain) than the modules that make up say a typical Java program
|
Large modules imply looser synchronization constraints and the asynchronous communication model we described
-
parallel computing involves tight synchronization and messaging between smaller modules with less geographical distribution
|
