cta-wave / common-media-client-data

A repository to collect discussion and feedback on the Common Media Client Data proposal.
30 stars 0 forks source link

Better naming for the modes? #128

Closed acbegen closed 4 months ago

acbegen commented 5 months ago

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.

PCaponetti commented 4 months ago

Paul to take some homework to come up with 5 options here.

nicolaslevy commented 4 months ago

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

wilaw commented 4 months ago

+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

PCaponetti commented 4 months ago

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.

PCaponetti commented 4 months ago

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.

piersoh commented 4 months ago
  1. origin
  2. alternate
  3. alternate-state-periodic (alternate-sp)
wilaw commented 4 months ago

We decided on

Also tightened language around timing , reporting delay and recommended intervals.