version 1.25, 2001/07/06 04:27:20
|
version 1.28, 2001/07/08 03:41:33
|
|
|
| |
|
- 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. | - Revisit use of namespace v.s. objectName in all CIM operations. |
| |
- What do we do when getInstance() is called and the nameSpace is | - What do we do when getInstance() is called and the nameSpace is |
|
|
| |
- 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. |
|