|
version 1.1, 2001/06/03 23:45:23
|
version 1.2, 2001/06/05 12:08:42
|
|
|
|
| registration class. I suggest that for the moment, the provider qualifier | registration class. I suggest that for the moment, the provider qualifier |
| is by far the easiest and can be implemented now.</p> | is by far the easiest and can be implemented now.</p> |
| | |
| |
<p>The "interface specific text" is given to the provider interface once it is found, so it can use it to find the appropriate provider. </p> |
| <h3>Functions Needed</h3> | <h3>Functions Needed</h3> |
| | |
| |
<p>The only component within the CIMOM that deals directly with provider interfaces is the provider manager |
| |
(ProviderTable today). NOTE: We will change the name at some point of the |
| |
ProviderTable to ProviderManager. The provider manager is the provider interface |
| |
multiplexor.</p> |
| |
|
| |
<p>The functions we need:</p> |
| |
|
| <p>1. Find the interface modules. It may be logical to load these all at | <p>1. Find the interface modules. It may be logical to load these all at |
| startup rather than loading each one when one of its corresponding providers is | startup rather than loading each one when one of its corresponding providers is |
| loaded.</p> | loaded.</p> |
Return to
CreatingMultipleProviderInterfaces.htm
CVS log
Up to [Pegasus] / pegasus / doc / WorkPapers