(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.1 and 1.2

version 1.1, 2001/01/24 14:18:49 version 1.2, 2001/02/02 18:48:20
Line 1 
Line 1 
 /* /*
         $Log$         $Log$
           Revision 1.2  2001/02/02 18:48:20  karl
           Doc++ expansion
   
         Revision 1.1  2001/01/24 14:18:49  karl         Revision 1.1  2001/01/24 14:18:49  karl
         import Dev Doc Files         import Dev Doc Files
  
         $Author$         $Author$
 */ */
 /** @name Pegasus MSB Interfaces /** @name Pegasus MSB Interfaces
 The Pegasus MSB interfaces with 3 different entities:  The Pegasus MSB interfaces with several different entities:
  
 <UL> <LI> Providers <UL> <LI> Providers
      <LI> 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
 </UL> </UL>
  
Line 17 
Line 20 
 required by the broker. required by the broker.
  
 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>Client Interface</B>
   
   
   <B>Provider Interface</B>
   
   In Pegasus, the provider is a separate executable that accesses the
   managed resources and is used by the CIMOM to provide access to
   data. Providers forward this information to the CIMOM for
   integration and interpretation. When the CIMOM receives a
   request from a management application for data that is not available from the
   CIMOM Repository, it forwards the request to a provider. The
   CIMOM Repository only contains static data.
   Providers implement a provider interface that supports the type of service
   specific to their role. In order to implement the interface, a provider class
   must first declare the interface in an implements clause, and then it must
   provide an implementation (a body) for all of the abstract methods of
   the.interface.
   
   
   <Services Interface</B>
   
   ATTN: Need to put something here.
   
   <B>Repository Interface</B>
   
   The repository interface isused by the CIMOM to  interface with implementations of the repository thatstore and
   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.
   
   .
 */ */
  


Legend:
Removed from v.1.1  
changed lines
  Added in v.1.2

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2