Closed acbegen closed 4 months ago
Paul to take some homework to come up with 5 options here.
Idea: we can name the mode according to what generates the event of sending the information (CMCD). Something like:
Mode 1: request mode Mode 2: response mode Mode 3: state-interval mode
+1 to https://github.com/cta-wave/common-media-client-data/issues/128#issuecomment-2194998267
We could also use the 'on-' prefix to indicate that the differentiation is when the data is transmitted, as 'request' has a pretty broad meaning in IT.
Mode 1: on-request mode Mode 2: on-response mode Mode 3: on-state-interval mode
I do really like the suggestion from Nicolas and enhancement from Will. In the interest of completeness and finishing my homework, here are a few more ideas:
Standard Remote Summary
Inline Out of band (OOB) Snapshot
Piggyback Independent (one of the ones from above?)
To be clear, I'm not liking any of these as much as what has been suggested already.
Going with Nicolas' original request, as the on-
prefix led to a bit of confusion and bikesheding. We can change later if there is genuine confusion.
We decided on
Also tightened language around timing , reporting delay and recommended intervals.
Mode 1: Default mode Mode 2: Per-response mode Mode 3: Per-interval mode
I know mode 3 is also triggered upon state changes, but then the term "interval" still applies IMO.