From a component point of view, we decided to do the architectural design based on a layered solution to the problem.

Transport layer: responsible for handling all communications between hosts.

Remote Reference layer: responsible for managing and keeping all references to objects.

Stub/Dispatcher layer:aware of the invocation and execution (respectively) of the methods exported by the objects.

Service Layer: Activation, DGC, Registry.

DGC can be located at both client and server, and is responsible for reference counting and talking to local GC in order to free no-longer referenced resources. DGC component is built on top of the stack.

Activator is also designed as a remote object specific app, so it sits on top of the stack.

Registry is also designed as a "bootstrapped" remote object.

Class Diagrams

Sequence Diagrams