|
version 1.2, 2001/02/02 18:48:20
|
version 1.3, 2001/02/02 19:38:23
|
|
|
|
| /* | /* |
| $Log$ | $Log$ |
| |
Revision 1.3 2001/02/02 19:38:23 karl |
| |
add graphic |
| |
|
| Revision 1.2 2001/02/02 18:48:20 karl | Revision 1.2 2001/02/02 18:48:20 karl |
| Doc++ expansion | Doc++ expansion |
| | |
|
|
|
| /** @name Architecture | /** @name Architecture |
| | |
| | |
| ATTN: Not complete |
|
| |
|
| This section defines the overall architecture of the Pegasus implementation. | This section defines the overall architecture of the Pegasus implementation. |
| | |
| |
@name Design Goals |
| | |
| |
We set some basic design goals early in the development of Pegasus as follows: |
| |
<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>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>Open to a wide range of specialization and customization. |
| |
<LI>Minimize the functionality of the basic core CIMOM. We wanted to create an environment where the majority of customization could be created by working with attached modules that would both extend and modify the functionality of the broker. |
| |
<LI>Use only open source components in the pegasus environment |
| |
<LI>Design for maximum portability. The initial targets would be Linux, Unix, and NT but the product should be usable in a wide variety of platforms and platform sizes. |
| |
<LI>The APIs and interfaces should be clear, given that they are in C++ |
| |
<LI> |
| |
</UL> |
| */ | */ |
| | |
| //@{ | //@{ |
Return to
architecture.dxx
CVS log
Up to [Pegasus] / pegasus / doc / DevManual