DSOM features
Here is a quick summary of some of DSOM's more important features:
- Uses the standard SOM Compiler, Interface Repository,
language bindings, and class libraries. Thus, DSOM provides a growth path
for non-distributed SOM applications.
- Allows an application program to access a mix of local
and remote objects. The fact that an object is remote is transparent to
the program.
- Provides run-time services for creating, destroying,
identifying, locating, and dispatching methods on remote objects. These
services can be overridden or augmented to suit the application.
- Uses existing interprocess communication (IPC) facilities
for Workstation communication, and common local area network (LAN) transport
facilities for Workgroup communications. Support for TCP/IP, Netware IPX/SPX,
and NetBios is provided. DSOM communications is extensible in that an application
can provide its own transport.
- Provides support for writing multi-threaded servers
and event-driven programs.
- Provides a default object server program, which can
be easily used to create SOM objects and make those objects accessible
to one or more client programs. If the default server program is used, SOM
class libraries are loaded upon demand, so no server programming or compiling
is necessary.
- Complies with the CORBA 1.1 specification, which is
important for application portability.
[Back: What is Distributed SOM?]
[Next: When to use DSOM]