AMWA IS-05 NMOS Device Connection Management Specification (Stable)
Examples for release v1.1.0
- base-get-200
- bulk-base-get-200
- bulk-post-confirm
- bulk-post-fail
- bulk-receiver-post
- bulk-sender-post
- receiver-active-get-200-mqtt
- receiver-active-get-200-uninit
- receiver-active-get-200
- receiver-constraints-get-200-2022-7
- receiver-constraints-get-200-mqtt
- receiver-constraints-get-200-websocket-ext
- receiver-constraints-get-200
- receiver-get-200-uninit
- receiver-get-200
- receiver-patch-absolute
- receiver-patch-activation-only
- receiver-patch-redundant-streams
- receiver-patch-relative
- receiver-patch-transportfile
- receiver-patch-unicast
- receiver-patch
- receiver-pending-get-200
- receiver-resource-get-200
- receiver-stage-scheduled-absolute
- receiver-stage-scheduled-relative
- receiver-stage-scheduled-transportfile
- receiver-stage-success-redundant-streams
- receiver-stage-success
- resource-get-200
- resourcelist-get-200
- sender-active-get-mqtt
- sender-active-get-uninit
- sender-active-get
- sender-constraints-get-200-2022-7
- sender-constraints-get-200-mqtt
- sender-constraints-get-200-websocket-ext
- sender-constraints-get-200
- sender-get-200-uninit
- sender-get-200
- sender-patch-absolute
- sender-patch-activation-only
- sender-patch-redundant-streams
- sender-patch-relative
- sender-patch-unicast
- sender-patch
- sender-resource-get-200
- sender-stage-absolute-success
- sender-stage-relative-success
- sender-stage-success-redundant-streams
- sender-stage-success
- single-root
- stage-error
- stage-fail
- transporttype-get