Summary
Instantiating an OSID Provider
OSID Providers are instantiated through the runtime using the osid.OsidRuntimeManager interface. You can think of the OsidRuntime as a service bus from which OSID Providers can be accessed. The three pieces of information getManager() requires are:
- OSID: this is an enumerated list of OSID Packages defined in osid.OSID
- implementation name: the name of the OSID Provider implementation (in Java, this is the class name of the OsidManager)
- version: the OSID Specification version required by the OSID Consumer (not the implementation version)
If successful, the OsidManager for the requested OSID will be returned. The OsidManager represents the principal service endpoint into the OSID Provider.
OsidManagers & OsidSessions
OSIDs are sliced into small clusters of functionality. These slices appear as sub-interfaces (not to be confused with sub packages) called OsidSessions. OsidSessions do the heavy lifting and are accessed through OsidManagers.
Accessing OsidManagers in Sub Packages
Sub Packages have their own service access through an OsidManager. The OsidManager of the sub package is accessed by way of the OsidManager in the parent package.