Designing a child caller

Child callers function just like parent callers, except that a child caller keeps track of its child ID which allows it to connect with its corresponding child dispatcher. You do not need to manage the child ID yourself. As long as your child caller class derives from MRemoteCallerChild, the child ID process is transparent to the caller.

A child caller must also derive from the abstract child base class. This provides the caller stubs with an interface matching that of the remote member function. Other than using this method of derivation, a child caller does not require any code specific to the child object architecture.