MAK RTIspy API Documentation for HLA 1.3
The RTI Managers

As mentioned in the previous section, the DtRtiAmbassadorImplementor delegates to, or uses, various manager classes and other objects to perform most of the actual implementation of RTI services.

The managers are also where most of the state of the LRC resides. The managers are:

The DtFederateManager is instantiated by the RTI ambassador DtRtiAmbassadorImplementor. The DtFederateManager instantiates the DtConnectionMgr. The DtFederateManager and DtConnectionMgr are needed by both joined and unjoined federates. The other managers are not instantiated until the joinFederationExecution() call, since they are only used by a joined federate, and depend on FOM data, which is not available until the federate is joined. The RTI adds DDM functionality to the DtObjectManager and the DtInteractionManager by deriving new classes DtObjectDataDistMgr (objDdmMgr.h) and DtInterDataDistMgr (interDdmMgr.h). These classes are further derived for the 1.3 and 1516 specifications. When DDM services are enabled, these classes are instantiated instead of the base classes. When DDM services are disabled, the base classes are instantiated.

Pointers to all of the managers are available through DtRtiAmbassadorImplementor's accessors.

For information about the various functions that you can use to inspect or alter the portion of the LRC's state managed by each manager, please see the class definitions for the managers.

Note:
The 1516 RTIspy APIs have the same internal components and managers as the 1.3 RTIspy API. The classes may have been modified to some degree (for example, RTI type replacement), but they essentially perform the same functions.

[<< Introduction to the RTIspy API] [Home] [Top of Page] [Initializing a Plug-in >>]


Document ID: Generated on Thu Jun 14 14:15:04 EDT 2012 from SVN revision 116116
Copyright © 2005-2012 VT MÄK Inc. All Rights Reserved (www.mak.com)