The dynamically configurable distributed object (DCDO) model helps enable object evolution and facilitate the development of distributed objects from multiple independent implementation components. Using DCDOs, programmers can evolve existing active objects to accept new member functions, to change the interface and behavior of their member functions, and to remove member functions from their public or private interface. Programmers can make these changes on the fly, without deactivating any part of the system, without replacing binary executables, without interrupting the clients of evolving objects, and without having to know what the changes will be at the time the objects are initially compiled and run. The model supports evolution management strategies that define when and how object types evolve from one version to the next, and determine when a type change is propagated to existing instances. DCDOs represent a useful way to evolve active distributed objects in a wide area distr...
Michael J. Lewis, Andrew S. Grimshaw