- Modular & Persistent components/servers/objects.
- We want the servers to persist across each invocation
rather than having lenghty startup times for each call.
Additionally, we want a system that will allow good
software design of the components so that they can be
reused in different situations.
- Inter-component communication.
- PVM/MPI are inter process communication tools. A more
beneficial level is inter-object communication.
PVM/MPI can be extended in this way but require significant
modification. RMI, CORBA and perhaps WebObjects do this immediately.
- Multi-directional and loop communication.
- Thread support so that Client A can invoke method in
Server B which can implement its method by using an
object in A's process.
- Multi-lingual communication with support for
common languages and extensibility.
- C, C++ (by inclusion, Fortran), Java, Perl,
R/S, Xlisp-Stat, Matlab/Octave, SAS
- Self Describing Objects/Methods
- Necessary so that we can do dynamic discovery and invocation
of new methods without compilation. This is the DII in CORBA.
- Structured Programming -
- strong type checking in
the server's own language.
- Exceptions.
-
-
- Transparent Web access as component of network.
- We neither want the Web to be the focus of the
communication but want to allow different configurations of
clusters and servers. Likewise, we don't want the Web access
to be a special case requiring excessive work or
modification to the code of the servers.
- Synchronous and asynchronous invocation.
- This is blocking and non-blocking calls from the client as opposed to
multi-threaded servers.
- Support for different interfaces - GUIs, command line, etc.
- Additional High level services
- Load Balancing, security, naming, licensing, events,
concurrency, transactions, etc.
- Supporting Tools
- Debuggers, etc.
Duncan Temple Lang
<duncan@research.bell-labs.com>
Last modified: Tue May 19 13:54:48 EDT 1998