1 karl  1.1 /*

 2 karl  1.5 

 3 karl  1.1 */

 4 karl  1.4 /** @name Pegasus Interfaces

 5 karl  1.2 The Pegasus MSB interfaces with several different entities:

 6 karl  1.1 
 7           <UL> <LI> Providers

 8 karl  1.2      <LI> Services (Including respositories and other services)

 9 karl  1.1      <LI  Clients which may be either connectors or application consumers

10 karl  1.4      <LI> Repository

11 karl  1.1 </UL>
12           
13           Further, it includes both the APIs and the definitions of CIM data that are
14           required by the broker.
15           
16           Pegasus has effectivly implemented the same operations and data defintions across all of these interfaces with minor differences because of the special characteristics of each interface.

17 karl  1.2 

18 karl  1.4 <B>CIM Operations over HTTP</B>

19 karl  1.3 The core operations implemented in Pegasus are based entirely on the CIM operations over HTTP definitions by the DMTF in CIM Operations over HTTP specificaiton.
20           
21           The creation of all Pegasus interfaces is based on this core was a key objective in the design of Pegasus. These operations provide the creation, deletion, manipulation of CIM classes and objects and their components.
22           
23           Pegasus implements these operations as methods in the Pegasus class Operations The interfaces for this class and methods is defined in the header file operations.h.
24           

25 karl  1.2 <B>Client Interface</B>

26 karl  1.3 In Pegasus the client is a separate component that can communicate with the Pegasus server either through the WBEM CIM/XML protocol or directly through the Pegasus Client C++ Interfaces.

27 karl  1.2 

28 karl  1.3 The Client interfaces are an extension of the Pegasus Operations interfaces with some specific methods added for client/server communication control.

29 karl  1.2 

30 karl  1.4 <B>Provider Interfaces</B>

31 karl  1.2 
32           In Pegasus, the provider is a separate executable that accesses the
33           managed resources and is used by the CIMOM to provide access to
34           data. Providers forward this information to the CIMOM for
35           integration and interpretation. When the CIMOM receives a
36           request from a management application for data that is not available from the
37           CIMOM Repository, it forwards the request to a provider. The
38           CIMOM Repository only contains static data.
39           Providers implement a provider interface that supports the type of service
40           specific to their role. In order to implement the interface, a provider class
41           must first declare the interface in an implements clause, and then it must
42           provide an implementation (a body) for all of the abstract methods of
43           the.interface.
44           
45           

46 karl  1.4 <Services Interfaces</B>

47 karl  1.2 
48           ATTN: Need to put something here.
49           

50 karl  1.4 <B>Repository Interfaces</B>

51 karl  1.2 
52           The repository interface isused by the CIMOM to  interface with implementations of the repository thatstore and
53           retrieve provide persistence for class and instance information. 
54           
55           A prototype implementation of both a class and instance provider is provided with Pegasus (ATTN: SEE ALSO). However, it is expected that this will be replaced in many installations.
56           .

57 karl  1.1 */
58