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
In general, NMOS specs are written to allow redundancy and versioning of locators, e.g. by array properties for endpoints/URLs in various places in IS-04 and IS-05. The new "connection_uri" transport property is singular (and cannot be an array due to the schema for properties).
Is this a problem?
The text was updated successfully, but these errors were encountered:
The /constraints endpoint can of course enumerate multiple possibilities for "connection_uri", but that's not quite the same thing as having multiple URLs active simultaneously...
When considering this initially I wondered if this ought to be another case where multiple 'legs' in the transport_params array is used. Each leg would have to correspond to an IS-04 interface_binding as before.
Ah, yes, hmmmm. Makes sense - different URLs represent different redundant endpoints - but (perhaps not in this case but in other imagined similar ones) it could be that many/all of the other transport parameters had to be common between all the 'legs', which makes updating them interesting?
In general, NMOS specs are written to allow redundancy and versioning of locators, e.g. by array properties for endpoints/URLs in various places in IS-04 and IS-05. The new
"connection_uri"
transport property is singular (and cannot be an array due to the schema for properties).Is this a problem?
The text was updated successfully, but these errors were encountered: