Users will not be forced to use these implementations, however, particularly if they do not meet the users' performance, security, or functionality requirements. Core Legion objects provide the mechanisms that classes use to implement policies appropriate for their instances. Examples of core objects include hosts , vaults , contexts , binding agents , and implementations . Each method has a signature that describes the parameters and return value, if any, of the method. The complete set of method signatures for an object fully describes that object's interface, which is determined by its class.
Legion implements a three-level naming system.
At the highest level, users refer to objects using human-readable strings, called context names . Legion will contain too many objects to simultaneously represent all of them as active processes. Therefore, Legion requires a strategy for maintaining and managing the representations of these objects on persistent storage. A Legion object can be in one of two different states, active or inert . The OPR contains state information that enables the object to move to an active state.