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
Not currently, but this is an interesting question. What is the use case? During stream creation, a receiver can specify "events_requested", and understand which event types the transmitter supports and agrees to deliver through "events_supported" and "events_delivered" respectively. This will help receivers understand what they can request and get, but I don't know if that is what you are looking for.
Thinking about ways an organization might leverage multiple feeds for SETs, is there a method to scan for usable SSF RISC API transmitters?
The text was updated successfully, but these errors were encountered: