version 1.21, 2001/06/22 04:30:19
|
version 1.29, 2001/07/08 05:37:09
|
|
|
| |
|
- Note that it is possible to remove an class and still have association |
|
classes which refer to it. |
|
|
|
- Class inheritance not taken into consideration when resolving the |
|
AssocClass |
|
|
|
- It seems that associatios() will fail when AssocClass is a super |
|
class of the class which is in the association instance table. |
|
|
|
- Should there be a single associations table for the entire repository |
|
or should there be one per namespace as there is now? |
|
|
|
- If it is the case that a reference may only refer to an instance, |
|
then we must derive new types for representing object paths. |
|
|
|
- Many CIM operations interfaces are incorrect: GetInstance() for example |
|
takes a namespace and a CIMReference (which also may contain the |
|
namespace). According to the standard, it should take an "InstanceName". |
|
|
|
- Need way of signaling the cimserver so that it will reload the |
|
class inheritance table (after a MOF compile). |
|
|
|
- Revisit use of namespace v.s. objectName in all CIM operations. |
|
|
|
- What do we do when getInstance() is called and the nameSpace is |
|
provided both as an argument and as part of the instance name? |
|
|
|
- ReferenceNames should return classes not just instances? |
|
|
|
- Remove final const from const methods in non-const CIM element classes. |
|
|
|
- Null vs. empty CIM/HTTP parameters. |
|
|
|
- Resolve constness problems. (get rid or Const classes?) |
|
|
|
- Change CIMReference to CIMObjectPath? |
|
|
|
- Finish associations. |
|
|
|
- Provide CIMOM Context. |
|
|
|
- Complete conventions document. |
|
|
|
- The CIMServer.exe program should probably create the logs directory |
|
under PEGASUS_HOME. |
|
|
|
- Clean up exceptions. |
|
|
- Resolve redundancy in which the namespace is passed to certain methods | - Resolve redundancy in which the namespace is passed to certain methods |
(getClass) and the CIMReference itself may contain a namespace arguent. | (getClass) and the CIMReference itself may contain a namespace arguent. |
| |
|
|
| |
- Figure out how inheritance of keys works. | - Figure out how inheritance of keys works. |
| |
- Investiage weak assocations. |
- Investigage weak associations. |
| |
- Enforce constraint qualifiers. | - Enforce constraint qualifiers. |
| |
|
|
- Support multiple providers of the extact same class. | - Support multiple providers of the extact same class. |
DiskController example and LanController. | DiskController example and LanController. |
| |
- SLP |
- SLP - Eliminate lib directory. |
- Eliminate lib directory. |
|