Concurrency Configuration
Playback concurrency allows Lura Player to identify a viewer session and enforce the maximum number of concurrent playback sessions allowed for an account. This feature requires Akta Cloud.
To enable concurrency handling, add the "concurrency" object to your player configuration.
| Attribute | Type | Description |
|---|---|---|
| enabled | boolean | Whether concurrency handling is enabled. |
| accountId | string | Account identifier used for concurrency checks. |
| deviceId | string | Device identifier used for concurrency checks. |
| max | number | Maximum number of allowed concurrent playback sessions. |
danger
Always use quoted keys (e.g., "accountId" instead of accountId) when defining configuration objects in BrightScript.
Concurrency Example
m.player.callFunc("setConfig", {
...
"lura": {
"appKey": "<YOUR_APP_KEY>",
"assetId": "<ASSET_ID>"
},
"concurrency": {
"enabled": true,
"accountId": "<ACCOUNT_ID>",
"deviceId": "<DEVICE_ID>",
"max": 2
}
...
})
When the concurrency limit is reached, playback is blocked and the player emits the CONCURRENCY_LIMIT_REACHED error with code 1901.