Channel identifiers for large scale games
Use channel identifiers for large-scale game servers with Vivox.
읽는 시간 1분최근 업데이트: 8달 전
If either of the following statements are true, then use caution when constructing your channel identifiers:
- You expect your application to exceed 100,000 PCU
- You expect to use the multichannel feature
You can split large scale games across multiple physical audio servers ("shards") at the discretion of Vivox Operations. Construct your channel identifiers to use the following format:
shard-group
For example, consider the application "Queen of the Death" (QotD), which allocates users according to geographical region, for example,"NA" for "North America". Assume that QotD joins a 3D channel for all participants in a match, and then also joins a 2D channel for members of a squad. In this case, the best practice for QotD is to apply the following criteria:
- Use a hash to identify the match.
- Include the region and match identifiers in the "shard" portion of the channel identifier.
- Include the 3D and squad identifiers after the "shard" portion of the channel identifier.
The match identifier assigned for this match is , and the 3D space is . Further assume that squads are assigned integer IDs starting with 1.
d0634bad1ca5a9cdtundra-
3D channel URIsip:confctl-d-issuer.NA.d0634bad1ca5a9cd-tundra@example.vivox.com
-
2D channel URI for squad 1sip:confctl-g-issuer.NA.d0634bad1ca5a9cd-1@example.vivox.com
-
2D channel URI for squad 2sip:confctl-g-issuer.NA.d0634bad1ca5a9cd-2@example.vivox.com
참고
Failing to follow these guidelines might result in multichannel users not all being co-located on the same shard.