...
| # | Issue | Notes | Decision |
|---|---|---|---|
| 1 | Is it intended that CM Notification subscription request cover (all) descendants of the given xpath too?! | e.g.. if a child is removed and there is a subscription for the parent node, will a notification be send (grandchild, child leaf updates etc.) I hope NOT! Consider:
| |
| 2 | Could xpath point to an element that does not exist (yet) | if not how, how can I client be informed about a create event? | |
| 3 | Should NCMP support re-homing, moving of a CM Handle from one DMI to another? | assume only trough delete & create | |
| 4 | CM Handle Delete: Should DMI or Clients be sent a subscription update (assume no) | do NOT delete dmi-subscription entry until owning subscription is deleted (just ignore upon future delete if cm handle is gone altogether) | |
| 5 | Validation of xpath | options order of implement and also performance cost!
| |
| 6 | can DMI plugin 'reject' a subscription create (for a given cm-handle-xpath combination) | As NCMP might not validate as per issue#5 the DMI=plugin or component further down might have to reject an invalid xpath... | yes currently DMI can use response to say which cm handles are not accepted i.e. rejected' (but not 'pending') |
| 7 | implementation question: should 'rejected' DMI-subscriptions be stored | I would think not | |
| 8 | Dimensioning of DB depends on #cm handles, #subscriptions and #xpaths per subscription, this could be too big for fast processing of updates! | Need to agree maximum and possibly realistic average/total number of entries based on the characteristics above The team is blocked until this becomes clear as it wil affect the way the data needs to be modelled exactly | |
| 9 | Maximum (error) message size, | theoretically theoretically all cm handles and all xpaths combinations could be rejected or pending leading to a very large error message! | |
| 10 | can each CM-Handled have different set of xpaths(s) per subscription | teh the current 'basic' solution only supports a common set of daatstoredatastore/xpaths (filter) | |
| 11 | can the same cm handle/xpath have different subscriptions with different datastores, does that affect the cm data notifications send (which datastore applies) |
Solution Proposals
Current state handling for 'basic' (not merged) subscription create/delete (under development)
...