...
| # | Issue | Notes | Decision |
|---|---|---|---|
| 1 | Do we need a analysis template? | is convention for (new) developers to guide them | Luke Gleeson (Unlicensed) and Toine Siebelink agreed we do to have consistent pages |
| 2 | This is an open issue | ||
| 3 | This is a very important (blocking issue) |
...
| Possible Topic Names (TBD) | |||
| 4 |
|---|
Possible Topic Names
| # | Source | Content | Topic Name | Destination |
|---|---|---|---|---|
| 1 | NCMP | Forwarded Subscription Event | TBD (cm-avc-subscription-forwarded) | DMI Plugins |
| 2 | DMI Plugins | Forwarded Subscription Event Response | TBD (cm-avc-subscription-forwarded-response) | NCMP |
| 3 | NCMP | Subscription Event Outcome | TBD (cm-avc-subscription-outcome-response) | Client Apps |
Any Other Header
...
Implementation Details
- The NCMP component could utilize a Hash Map to store request_id and timestamp the time that message is published into the topic mentioned in #1 → Possible Topic Names
- In order to calculate the Subscription Create Outcome Message, the NCMP component should consume response messages from the topic mentioned in #2 → Possible Topic Names
The NCMP component should consume messages as per the timeframe periods, and compare request ids with the ones that already kept in that Hash Map at step 1. - If the incoming request id is found in the Hash Map, the total time elapsed could be calculated via timestamp (responses read) minus timestamp from Hash Map (for related request id).
- The NCMP can populate Subscription Event Outcome report, and publish it to the topic mentioned in #3 → Possible Topic Names