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
Hello folks,
We're using this client in a docker image bundled by @rhastie. Our registered end devices supports different versions of NMOS APIs but they may not overlap. So we need to go back and forth in the setting page to modify the Query API version to see them appear in the Node list.
Would it make more sense to use all the Query API versions by default to see all these Nodes simultaneously?
Thanks
PK
The text was updated successfully, but these errors were encountered:
In this example there are several possible kinds of query a client could make on R...
Query on R v1.3 shows A and C, but not B
Query on R v1.2 shows A, B and C (you may find this surprising?) but strips out v1.3-specific properties of A and C
Query on R v1.3 with api.downgrade=v1.2 also shows A, B and C but doesn't strip the v1.3 properties, but is more challenging for a client to handle because it has no way to tell which version it is getting
The nmos-js does not support using api.downgrade right now.
I've just realized that I was confused by some disconnecting devices. Everything looks normal now, regarding what you describe.
Thanks for clarifying, @garethsb . You can close this.
Hello folks,
We're using this client in a docker image bundled by @rhastie. Our registered end devices supports different versions of NMOS APIs but they may not overlap. So we need to go back and forth in the setting page to modify the Query API version to see them appear in the Node list.
Would it make more sense to use all the Query API versions by default to see all these Nodes simultaneously?
Thanks
PK
The text was updated successfully, but these errors were encountered: