Reasons Alternative Architecture
Simpler architecture: less wrappers, just one protocol on client side
No direct linking with legacy code also for CORBA-wrappers, different sites for wrapper and legacy megamodule possible
All native CHAIMS-megamodules will be built using wrapper templates ==> no reason for several protocols, they can all use TCP/IP.
Dataflow-optimization: direct messages between megamodules/their wrappers necessary (without bridges)
Thin client that could run everywhere (TCP/IP is available everywhere, but not CORBA or DCE, RMI also is easily available everywhere).
CSRT could be implemented by interpreter instead of compiler, maybe also possible with current architecture, but more complex.
We use just transport-facility (really true? what about native CHAIMS-types like string, integer, boolean?) of CORBA, RMI, DCE (for data we have ASN.1); this is already offered by TCP/IP ==> no unnecessary overkill
Drawback: missing one of the current funding objectives (heterogeinity on client side).