1 karl  1.1 /*

 2 karl  1.2     $Log: cimobjects.dxx,v $

 3 karl  1.3     Revision 1.2  2001/02/05 14:14:00  karl
 4               doc++ extension for respository
 5           

 6 karl  1.2     Revision 1.1  2001/02/02 18:48:20  karl
 7               Doc++ expansion
 8           

 9 karl  1.1 */
10           /** @name CIM Objects in Pegasus
11           
12           The Common Information model (CIM) consists of a number of basic objects
13           defined in the CIM specification.  This includes:
14           <UL>
15           <LI>Classes \Ref{CLASS}
16           <LI>Instances of Classes \Rf{REFERENCE}
17           <LI>Qualifiers \Ref{QUALIFIER}
18           <LI>Properties
19           <LI>Methods
20           <LI>Arrays
21           </UL>
22           Pegasus implements representations of these objects in C++ classes and
23           provides methods for creation, manipulation, and deletion of the objects.
24           

25 karl  1.3 

26 karl  1.1 In addition, Pegasus implements a number of the key concepts built into CIM as objects including:
27           <UL>
28           <LI> Scope
29           <LI> Flavor

30 karl  1.2 <LI>Object Path
31           <LI>etc.

32 karl  1.1 </UL>
33           

34 karl  1.3 Much of the programming of the Pegasus object broker, clients, and in particular providers and service extensions in the Pegasus envrinment depends on the use of these C++ representations of CIM Objects and concepts.
35           
36           Each Pegasus CIM C++ Object representation includes:

37 karl  1.1 

38 karl  1.3 <UL>
39           <LI>TConstructors and destructors
40           <LI>Methods for manipulation of sub-objects.  Thus, the class and instance classes provide for manipulation of the property, qualifier, and method objects that are contained in these classes.
41           <LI>Methods for finding sub-objects. Thus, the class and instance classes provide for finding property, qualifier, and method objects within an instnace of a CIMClass or CIMInstance. These methods are generally built around defining the name of the object to be found and having an index to that object returned.
42           <LI>Methods for comparison
43           <LI>Methods for cloning
44           <LI>Methods to convert the object to XML
45           <LI>Methods to convert the object to MOF (Planned)
46           </UL>
47           There is a class for every major CIM object and concept as shown in the table in \Ref{CIM Object Table}

48 karl  1.1 */