<LI><A NAME="tex2html1" HREF="node3.html#186">Industry three-tier view of enterprise =
computing</A>
<LI><A NAME="tex2html2" HREF="node5.html#187">Today's heterogeneous interoperating hybrid server
architecture.  High-performance commodity computing involves adding
high performance in the third tier.</A>
<LI><A NAME="tex2html3" HREF="node5.html#188">Integration of Object Technologies (CORBA) and the Web=3D
 </A>
<LI><A NAME="tex2html4" HREF="node8.html#189">Collaboration in today's Java Web Server implementation of the
three-tier computing model.  Typical clients (top right) are =
independent,
but Java collaboration systems link multiple clients through object
(service) sharing. </A>
<LI><A NAME="tex2html5" HREF="node10.html#190">
A parallel computer viewed as a single CORBA object in a classic
host-node computing model.  Logically, the host is in the middle tier
and the nodes in the lower tier.  The physical architecture could
differ from the logical architecture.</A>
<LI><A NAME="tex2html6" HREF="node10.html#191">Each node of a parallel computer instantiated as a CORBA
object. The ``host&quot; is logically a separate CORBA object but could
be instantiated on the same computer as one or more of the
nodes. Via a protocol bridge, one could address objects
using CORBA with local parallel computing nodes invoking MPI and
remote accesses using CORBA where its functionality (access to
many services) is valuable. </A>
<LI><A NAME="tex2html7" HREF="node10.html#192">A message optimization bridge allows MPI (or equivalently
Globus or PVM) and commodity technologies to coexist with a seamless
user interface. </A>
<LI><A NAME="tex2html8" HREF="node15.html#193">An architecture for an interpreted Java frontend
communicating with a middle-tier server controlling dynamically an
HPCC backend </A>
