(file) Return to interfaces.dxx CVS log (file) (dir) Up to [Pegasus] / pegasus / doc / DevManual

Diff for /pegasus/doc/DevManual/interfaces.dxx between version 1.2 and 1.5

version 1.2, 2001/02/02 18:48:20 version 1.5, 2005/12/14 18:38:54
Line 1 
Line 1 
 /* /*
         $Log$  
         Revision 1.2  2001/02/02 18:48:20  karl  
         Doc++ expansion  
  
         Revision 1.1  2001/01/24 14:18:49  karl  
         import Dev Doc Files  
   
         $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
Line 21 
Line 15 
  
 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>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 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.
   
   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.
   
 <B>Client Interface</B> <B>Client Interface</B>
   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.
  
   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
Line 40 
Line 43 
 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.
  
 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. 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.
   
 . .
 */ */
  

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.5
No CVS admin address has been configured
 Powered by
ViewCVS 0.9.2