You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Controller SHOULD use an IS-04 Query API WebSocket connection to monitor version timestamp increments on Senders and Receivers being controlled.
In Interoperability: IS-04: Discovery, it's mentioned that Devices advertise the Connection API and that when parameters of Senders or Receivers change, their IS-04 version is updated.
We think something needs to advertise when particular Senders or Receivers are added or removed from IS-05. This could be the IS-04 Sender or Receiver version (reflecting the presence/absense of the /x-nmos/connection/v1.1/senders/{senderId} URL path) or the Device version (reflecting the change to the /x-nmos/connection/v1.1/senders response).
The text was updated successfully, but these errors were encountered:
In the Controller spec document we now have:
In Interoperability: IS-04: Discovery, it's mentioned that Devices advertise the Connection API and that when parameters of Senders or Receivers change, their IS-04
version
is updated.We think something needs to advertise when particular Senders or Receivers are added or removed from IS-05. This could be the IS-04 Sender or Receiver
version
(reflecting the presence/absense of the /x-nmos/connection/v1.1/senders/{senderId} URL path) or the Deviceversion
(reflecting the change to the /x-nmos/connection/v1.1/senders response).The text was updated successfully, but these errors were encountered: