...
| Expand | ||
|---|---|---|
| ||
All connected and healthy players establish and keep persistent WebSocket connections with bsn.Content. If a player has "BSN" setup type and an active subscription, it will receive events from the server when either its settings or schedule are changed by any user in BrightAuthor:connected. The event propagation should take not more than few minutes (typically one minute), and the player requests the new settings or schedule immediately after receiving such an event. |
How
...
does
...
BSN.cloud
...
notify the player of new BrightAuthor:connected content?
| Expand | ||
|---|---|---|
| ||
If a player is active, has a WebSockets connection, and a change was made in the schedule or settings (not in the playlist or feed) the player gets only a notice, not the actual content. After getting the notice, it sends one or more requests to retrieve the updated Schedule/Settings. Dynamic Playlists, Tagged Playlists, Live Data Feeds and Live Media Feeds changes are propagated differently. Each of these entities has an underlying mRSS feed, and after retrieving them from the presentation, a player checks for changes in each feed separately with a frequency defined by the |
...