version 1.3, 2001/02/06 17:02:13
|
version 1.4, 2001/02/23 20:27:47
|
|
|
/* | /* |
$Log$ | $Log$ |
|
Revision 1.4 2001/02/23 20:27:47 karl |
|
correct documentation |
|
|
Revision 1.3 2001/02/06 17:02:13 karl | Revision 1.3 2001/02/06 17:02:13 karl |
rearrange documentation for interfaces | rearrange documentation for interfaces |
| |
|
|
| |
$Author$ | $Author$ |
*/ | */ |
/** @name Pegasus MSB Interfaces |
/** @name Pegasus Interfaces |
The Pegasus MSB interfaces with several different entities: | The Pegasus MSB interfaces with several different entities: |
| |
<UL> <LI> Providers | <UL> <LI> Providers |
<LI> Services (Including respositories and other services) | <LI> Services (Including respositories and other services) |
<LI Clients which may be either connectors or application consumers | <LI Clients which may be either connectors or application consumers |
|
<LI> Repository |
</UL> | </UL> |
| |
Further, it includes both the APIs and the definitions of CIM data that are | Further, it includes both the APIs and the definitions of CIM data that are |
|
|
| |
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. | 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. |
| |
<B>Implementing the CIM over HTTP Operations</B> |
<B>CIM Operations over HTTP</B> |
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. | 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. |
| |
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. | 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. |
|
|
| |
The Client interfaces are an extension of the Pegasus Operations interfaces with some specific methods added for client/server communication control. | The Client interfaces are an extension of the Pegasus Operations interfaces with some specific methods added for client/server communication control. |
| |
<B>Provider Interface</B> |
<B>Provider Interfaces</B> |
| |
In Pegasus, the provider is a separate executable that accesses the | In Pegasus, the provider is a separate executable that accesses the |
managed resources and is used by the CIMOM to provide access to | managed resources and is used by the CIMOM to provide access to |
|
|
the.interface. | the.interface. |
| |
| |
<Services Interface</B> |
<Services Interfaces</B> |
| |
ATTN: Need to put something here. | ATTN: Need to put something here. |
| |
<B>Repository Interface</B> |
<B>Repository Interfaces</B> |
| |
The repository interface isused by the CIMOM to interface with implementations of the repository thatstore and | The repository interface isused by the CIMOM to interface with implementations of the repository thatstore and |
retrieve provide persistence for class and instance information. | retrieve provide persistence for class and instance information. |