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

Diff for /pegasus/doc/DevManual/architecture.dxx between version 1.3 and 1.4

version 1.3, 2001/02/02 19:38:23 version 1.4, 2001/02/25 15:01:40
Line 1 
Line 1 
 /* /*
 $Log$ $Log$
       Revision 1.4  2001/02/25 15:01:40  karl
       Add frames to manual
   
 Revision 1.3  2001/02/02 19:38:23  karl Revision 1.3  2001/02/02 19:38:23  karl
 add graphic add graphic
  
Line 10 
Line 13 
 import Dev Doc Files import Dev Doc Files
  
 */ */
 /** @name Architecture  
  
   /** @name Pegasus Architecture
  
 This section defines the overall architecture of the Pegasus implementation. This section defines the overall architecture of the Pegasus implementation.
  
 @name Design Goals  */
   //@{
   /** @name Design Goals
  
 We set some basic design goals early in the development of Pegasus as follows:  The Pegasus design team set some basic design goals early in the development of Pegasus as follows:
 <UL> <UL>
 <LI>C++ as the core development language. We selected C++ because it represented a compromise between the ability to work with objects and a language that would be acceptable for high avaailablity platforms. <LI>C++ as the core development language. We selected C++ because it represented a compromise between the ability to work with objects and a language that would be acceptable for high avaailablity platforms.
 <LI>Modular Architecture - We wanted to be able to create the architecture based on well understand standardized modules that have clean well defined interfaces between the modules. <LI>Modular Architecture - We wanted to be able to create the architecture based on well understand standardized modules that have clean well defined interfaces between the modules.
Line 30 
Line 35 
 </UL> </UL>
 */ */
  
 //@{  
 /** @name Manageability Services Broker (MSB).  /** @name The Broker
  
 The Common Information Model Object Broker (often known as the CIM Information The Common Information Model Object Broker (often known as the CIM Information
 manager or CIMOM) brokers CIM objects between a number of sources and manager or CIMOM) brokers CIM objects between a number of sources and
Line 59 
Line 64 
  
 */ */
  
 /** @name Description of the CIMOM and WEBM  /** @name Functional Flow
  
 The Common Information Model Object Broker (often known as the CIM Information The Common Information Model Object Broker (often known as the CIM Information
 manager or CIMOM) brokers CIM objects between a number of sources and manager or CIMOM) brokers CIM objects between a number of sources and
Line 223 
Line 228 
 property, instance, method, and qualifier checkers and the rules ov validation defined by the CIM specification. These verifiers ensure that the CIM rules are enforced. This includes type verification,type conversions, verification of proper key usage, and other checks., property, instance, method, and qualifier checkers and the rules ov validation defined by the CIM specification. These verifiers ensure that the CIM rules are enforced. This includes type verification,type conversions, verification of proper key usage, and other checks.,
  
 */ */
   
 //@} //@}
   

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