@tencentcloud/sdk-mcp 1.3.4 → 1.3.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (105) hide show
  1. package/package.json +1 -1
  2. package/resource/doc/chatuikit/android/features/theme.md +363 -0
  3. package/resource/doc/chatuikit/android/workflow.md +0 -0
  4. package/resource/doc/chatuikit/{android/client_api_android.md → faq/android_sdk/client-api.md} +0 -1
  5. package/resource/doc/chatuikit/faq/{native_sdk/faq.md → common/product.md} +8 -0
  6. package/resource/doc/chatuikit/faq/flutter_sdk/faq.md +54 -0
  7. package/resource/doc/chatuikit/faq/web_sdk/faq.md +1 -1
  8. package/resource/doc/chatuikit/flutter/features/theme.md +379 -0
  9. package/resource/doc/chatuikit/flutter/workflow.md +816 -0
  10. package/resource/doc/chatuikit/iOS/features/theme.md +416 -0
  11. package/resource/doc/chatuikit/iOS/workflow.md +0 -0
  12. package/resource/doc/chatuikit/react/components/chat-setting.md +124 -0
  13. package/resource/doc/chatuikit/react/components/contact-list.md +1331 -0
  14. package/resource/doc/chatuikit/react/components/search.md +885 -0
  15. package/resource/doc/chatuikit/vue/components/chat-setting.md +88 -0
  16. package/resource/doc/chatuikit/vue/components/contact-list.md +679 -0
  17. package/resource/doc/chatuikit/vue/components/search.md +1384 -0
  18. package/resource/doc/livekit/live/android/workflow.md +137 -4
  19. package/resource/doc/livekit/live/flutter/live-audience-list.md +337 -0
  20. package/resource/doc/livekit/live/flutter/live-audio-effect.md +739 -0
  21. package/resource/doc/livekit/live/flutter/live-barrage.md +578 -0
  22. package/resource/doc/livekit/live/flutter/live-base-beauty.md +484 -0
  23. package/resource/doc/livekit/live/flutter/live-co-guest-interaction.md +606 -0
  24. package/resource/doc/livekit/live/flutter/live-gift.md +812 -0
  25. package/resource/doc/livekit/live/flutter/live-host-interaction.md +1113 -0
  26. package/resource/doc/livekit/live/flutter/live-integration.md +1029 -0
  27. package/resource/doc/livekit/live/flutter/live-live-list.md +861 -0
  28. package/resource/doc/livekit/live/ios/live-audience-list.md +335 -0
  29. package/resource/doc/livekit/live/ios/live-audio-effect.md +373 -0
  30. package/resource/doc/livekit/live/ios/live-barrage.md +529 -0
  31. package/resource/doc/livekit/live/ios/live-base-beauty.md +237 -0
  32. package/resource/doc/livekit/live/ios/live-co-guest-interaction.md +483 -0
  33. package/resource/doc/livekit/live/ios/live-gift.md +785 -0
  34. package/resource/doc/livekit/live/ios/live-host-interaction.md +743 -0
  35. package/resource/doc/livekit/live/ios/live-integration.md +822 -0
  36. package/resource/doc/livekit/live/ios/live-live-list.md +535 -0
  37. package/resource/doc/livekit/live/ios/workflow.md +352 -0
  38. package/resource/doc/rtcengine/faq/web/web.md +2 -2
  39. package/resource/doc/rtcengine/web/how_to_integrated_web_sdk.md +2 -2
  40. package/resource/doc/rtcengine/web/plugin/20-advanced-customized-capture-rendering.md +84 -0
  41. package/resource/doc/rtcengine/web/plugin/21-advanced-auto-play-policy.md +86 -0
  42. package/resource/doc/rtcengine/web/plugin/22-advanced-audio-mixer.md +220 -0
  43. package/resource/doc/rtcengine/web/plugin/23-advanced-support-detection.md +217 -0
  44. package/resource/doc/rtcengine/web/plugin/24-advanced-network-quality.md +137 -0
  45. package/resource/doc/rtcengine/web/plugin/25-advanced-device-change.md +97 -0
  46. package/resource/doc/rtcengine/web/plugin/26-advanced-publish-cdn-stream.md +453 -0
  47. package/resource/doc/rtcengine/web/plugin/27-advanced-small-stream.md +180 -0
  48. package/resource/doc/rtcengine/web/plugin/28-advanced-beauty.md +349 -0
  49. package/resource/doc/rtcengine/web/plugin/29-advanced-water-mark.md +149 -0
  50. package/resource/doc/rtcengine/web/plugin/30-advanced-cross-room-link.md +96 -0
  51. package/resource/doc/rtcengine/web/plugin/31-advanced-plugins-overview.md +405 -0
  52. package/resource/doc/rtcengine/web/plugin/34-advanced-proxy.md +244 -0
  53. package/resource/doc/rtcengine/web/plugin/35-advanced-ai-denoiser.md +84 -0
  54. package/resource/doc/rtcengine/web/plugin/36-advanced-virtual-background.md +202 -0
  55. package/resource/doc/rtcengine/web/plugin/37-advanced-voice-changer.md +98 -0
  56. package/resource/doc/rtcengine/web/plugin/38-advanced-basic-beauty.md +95 -0
  57. package/resource/doc/rtcengine/web/plugin/39-advanced-video-decoder.md +33 -0
  58. package/resource/doc/rtcengine/web/plugin/40-advanced-video-mixer.md +380 -0
  59. package/resource/doc/rtcengine/web/plugin/41-advanced-small-stream-auto-switcher.md +91 -0
  60. package/resource/doc/rtcengine/web/plugin/42-advanced-realtime-transcriber.md +314 -0
  61. package/resource/doc/rtcengine/web/plugin/43-advanced-face-detection.md +180 -0
  62. package/tools/chat/get-native-chat-feature-detail.js +30 -0
  63. package/tools/chat/get-native-chat-feature-detail.js.map +1 -0
  64. package/tools/chat/get-native-chat-integration.js +30 -12
  65. package/tools/chat/get-native-chat-integration.js.map +1 -1
  66. package/tools/common/get-faq.js +2 -4
  67. package/tools/common/get-faq.js.map +1 -1
  68. package/tools/definitions/get_native_chat_feature_detail_def.js +32 -0
  69. package/tools/definitions/get_native_chat_feature_detail_def.js.map +1 -0
  70. package/tools/definitions/get_native_chat_uikit_integration_def.js +18 -6
  71. package/tools/definitions/get_native_chat_uikit_integration_def.js.map +1 -1
  72. package/tools/definitions/{get_native_live_extra_features_def.js → get_native_live_uikit_extra_features_def.js} +3 -3
  73. package/tools/definitions/get_native_live_uikit_extra_features_def.js.map +1 -0
  74. package/tools/definitions/{get_native_live_interaction_def.js → get_native_live_uikit_interaction_def.js} +3 -3
  75. package/tools/definitions/get_native_live_uikit_interaction_def.js.map +1 -0
  76. package/tools/definitions/get_web_chat_uikit_component_detail_def.js +46 -7
  77. package/tools/definitions/get_web_chat_uikit_component_detail_def.js.map +1 -1
  78. package/tools/index.js +6 -4
  79. package/tools/index.js.map +1 -1
  80. package/tools/live/{get_native_live_extra_features.js → get_native_live_uikit_extra_features.js} +4 -4
  81. package/tools/live/get_native_live_uikit_extra_features.js.map +1 -0
  82. package/tools/live/{get_native_live_interaction.js → get_native_live_uikit_interaction.js} +4 -4
  83. package/tools/live/get_native_live_uikit_interaction.js.map +1 -0
  84. package/tools/rtcengine/get-trtc-web-sdk-faq.js +1 -1
  85. package/tools/rtcengine/get-trtc-web-sdk-plugin.js +45 -0
  86. package/tools/rtcengine/get-trtc-web-sdk-plugin.js.map +1 -0
  87. package/utils/handle-component-name.js +0 -16
  88. package/utils/handle-component-name.js.map +1 -1
  89. package/utils/report-cls-client.js +1 -1
  90. package/utils/report-es-client.js +1 -1
  91. package/resource/doc/chatuikit/android/integrate_tuichat_only_android.md +0 -382
  92. package/resource/doc/chatuikit/android/ui_api_android.md +0 -418
  93. package/resource/doc/chatuikit/iOS/integrate_tuichat_only_iOS.md +0 -993
  94. package/resource/doc/chatuikit/iOS/ui_api_iOS.md +0 -526
  95. package/tools/definitions/get_native_live_extra_features_def.js.map +0 -1
  96. package/tools/definitions/get_native_live_interaction_def.js.map +0 -1
  97. package/tools/live/get_native_live_extra_features.js.map +0 -1
  98. package/tools/live/get_native_live_interaction.js.map +0 -1
  99. /package/resource/doc/chatuikit/android/{integrate_tuikit_android.md → integration.md} +0 -0
  100. /package/resource/doc/chatuikit/{flutter/client_api_Flutter.md → faq/flutter_sdk/client-api.md} +0 -0
  101. /package/resource/doc/chatuikit/{iOS/client_api_iOS.md → faq/ios_sdk/client-api.md} +0 -0
  102. /package/resource/doc/chatuikit/flutter/{integrate_tuikit_Flutter.md → integration.md} +0 -0
  103. /package/resource/doc/chatuikit/iOS/{integrate_tuikit_iOS.md → integration.md} +0 -0
  104. /package/resource/doc/chatuikit/react/components/{chatheader.md → chat-header.md} +0 -0
  105. /package/resource/doc/chatuikit/vue/components/{chatheader.md → chat-header.md} +0 -0
@@ -0,0 +1,335 @@
1
+ `LiveAudienceStore` 是 `AtomicXCore` 中专门负责管理直播间观众信息的模块。通过 `LiveAudienceStore`,您可以为您的直播应用构建一套完整的观众列表及管理系统。
2
+
3
+ ![](https://write-document-release-1258344699.cos.ap-guangzhou.tencentcos.cn/100027182498/96da98a0ab3711f09b75525400bf7822.png)
4
+
5
+
6
+ ## 核心功能
7
+ - **实时观众列表**:获取并展示当前在直播间内的所有观众信息。
8
+
9
+ - **观众人数统计**:实时获取当前直播间的准确观众总数。
10
+
11
+ - **观众动态监听**:通过事件订阅,实时感知观众的加入和离开。
12
+
13
+ - **管理员权限**:主播可以将普通观众设为管理员,或撤销其管理员身份。
14
+
15
+ - **房间管理**:主播或管理员可以将任意普通观众请出(踢出)直播间。
16
+
17
+
18
+ ## 核心概念
19
+
20
+ 在开始集成之前,我们先通过下表了解一下 LiveAudienceStore 相关的几个核心概念:
21
+ <table>
22
+ <tr>
23
+ <td rowspan="1" colSpan="1" >**核心概念**</td>
24
+
25
+ <td rowspan="1" colSpan="1" >**类型**</td>
26
+
27
+ <td rowspan="1" colSpan="1" >**核心职责与描述**</td>
28
+ </tr>
29
+
30
+ <tr>
31
+ <td rowspan="1" colSpan="1" >`LiveUserInfo`</td>
32
+
33
+ <td rowspan="1" colSpan="1" >struct</td>
34
+
35
+ <td rowspan="1" colSpan="1" >代表一个观众(用户)的基础信息模型。它包含了用户的唯一标识 (`userID`)、昵称 (`userName`) 和头像地址 (`avatarURL`)。</td>
36
+ </tr>
37
+
38
+ <tr>
39
+ <td rowspan="1" colSpan="1" >`LiveAudienceState`</td>
40
+
41
+ <td rowspan="1" colSpan="1" >struct</td>
42
+
43
+ <td rowspan="1" colSpan="1" >代表观众模块的当前状态。其核心属性 `audienceList` 是一个 `[LiveUserInfo] `数组,存储了观众列表的快照;`audienceCount` 则代表当前观众总数。</td>
44
+ </tr>
45
+
46
+ <tr>
47
+ <td rowspan="1" colSpan="1" >`LiveAudienceEvent`</td>
48
+
49
+ <td rowspan="1" colSpan="1" >enum</td>
50
+
51
+ <td rowspan="1" colSpan="1" >代表观众动态的实时事件。分为 `.onAudienceJoined`(观众加入) 和 `.onAudienceLeft`(观众离开)两种,用于实现对观众列表的增量更新。</td>
52
+ </tr>
53
+
54
+ <tr>
55
+ <td rowspan="1" colSpan="1" >`LiveAudienceStore`</td>
56
+
57
+ <td rowspan="1" colSpan="1" >class</td>
58
+
59
+ <td rowspan="1" colSpan="1" >这是与观众列表功能交互的核心管理类。通过它,您可以获取观众列表快照、执行管理操作,并通过订阅其 `liveAudienceEventPublisher` 来接收实时动态。</td>
60
+ </tr>
61
+ </table>
62
+
63
+
64
+ ## 实现步骤
65
+
66
+ ### 步骤1:组件集成
67
+
68
+ 请参考 [开始直播](https://write.woa.com/document/191126382767431680) 集成 **AtomicXCore**,完成接入。
69
+
70
+ ### 步骤2:初始化并获取观众列表
71
+
72
+ 获取一个与当前直播间 liveId 绑定的 `LiveAudienceStore` 实例,并主动拉取一次当前的观众列表,用于首次展示。
73
+ ``` swift
74
+ import Foundation
75
+ import AtomicXCore
76
+ import Combine
77
+
78
+ class AudienceManager {
79
+ private let liveId: String
80
+ private let audienceStore: LiveAudienceStore
81
+ private var cancellables = Set<AnyCancellable>()
82
+
83
+ // 对外暴露【全量】观众列表的发布者,方便UI层订阅
84
+ let audienceListPublisher = CurrentValueSubject<[LiveUserInfo], Never>([])
85
+ // 对外暴露观众总数的发布者
86
+ let audienceCountPublisher = PassthroughSubject<UInt, Never>()
87
+
88
+ init(liveId: String) {
89
+ self.liveId = liveId
90
+ // 1. 通过 liveId 获取 LiveAudienceStore 的实例
91
+ self.audienceStore = LiveAudienceStore.create(liveID: liveId)
92
+
93
+ // 2. 订阅状态和事件
94
+ subscribeToAudienceState()
95
+ subscribeToAudienceEvents()
96
+
97
+ // 3. 主动拉取首屏数据
98
+ fetchInitialAudienceList()
99
+ }
100
+
101
+ /// 主动获取一次观众列表快照
102
+ func fetchInitialAudienceList() {
103
+ audienceStore.fetchAudienceList { [weak self] result in
104
+ switch result {
105
+ case .success:
106
+ print("首次拉取观众列表成功")
107
+ // 成功后,数据会通过下面的 state 订阅通道自动更新
108
+ case .failure(let error):
109
+ print("首次拉取观众列表失败: \(error.localizedDescription)")
110
+ }
111
+ }
112
+ }
113
+
114
+ // ... 后续代码
115
+ }
116
+ ```
117
+
118
+ ### 步骤3:监听观众列表状态与实时动态
119
+
120
+ 订阅 `audienceStore` 的 `state` 和 `event`,以接收全量列表快照和实时的观众进出事件,从而驱动 UI 更新。
121
+ ``` swift
122
+ extension AudienceManager {
123
+ /// 订阅 state,用于获取观众总数和列表快照
124
+ private func subscribeToAudienceState() {
125
+ audienceStore.state
126
+ .subscribe()
127
+ .receive(on: DispatchQueue.main)
128
+ .sink { [weak self] state in
129
+ // state.audienceList 是一个全量快照
130
+ self?.audienceListPublisher.send(state.audienceList)
131
+ // state.audienceCount 是实时总数
132
+ self?.audienceCountPublisher.send(state.audienceCount)
133
+ }
134
+ .store(in: &cancellables)
135
+ }
136
+
137
+ /// 订阅 event,用于处理观众的实时进出
138
+ private func subscribeToAudienceEvents() {
139
+ audienceStore.liveAudienceEventPublisher
140
+ .receive(on: DispatchQueue.main)
141
+ .sink { [weak self] event in
142
+ guard let self = self else { return }
143
+
144
+ var currentList = self.audienceListPublisher.value
145
+
146
+ switch event {
147
+ case .onAudienceJoined(let newAudience):
148
+ print("观众 \(newAudience.userName) 加入了直播间")
149
+ // 增量更新:在当前列表末尾添加新观众
150
+ if !currentList.contains(where: { $0.userID == newAudience.userID }) {
151
+ currentList.append(newAudience)
152
+ self.audienceListPublisher.send(currentList)
153
+ }
154
+
155
+ case .onAudienceLeft(let departedAudience):
156
+ print("观众 \(departedAudience.userName) 离开了直播间")
157
+ // 增量更新:从当前列表中移除离开的观众
158
+ currentList.removeAll { $0.userID == departedAudience.userID }
159
+ self.audienceListPublisher.send(currentList)
160
+ }
161
+ }
162
+ .store(in: &cancellables)
163
+ }
164
+ }
165
+ ```
166
+
167
+ ### 步骤4:管理观众(踢人与设置管理员)
168
+
169
+ 作为主播或管理员,对直播间内的观众进行管理操作。
170
+
171
+ #### 4.1 将观众踢出直播间
172
+
173
+ 调用 `kickUserOutOfRoom` 接口可以将指定用户请出直播间。
174
+ ``` swift
175
+ extension AudienceManager {
176
+ func kick(userId: String) {
177
+ audienceStore.kickUserOutOfRoom(userID: userId) { result in
178
+ switch result {
179
+ case .success:
180
+ print("成功将用户 \(userId) 踢出房间")
181
+ // 踢出成功后,您会收到 onAudienceLeft 事件
182
+ case .failure(let error):
183
+ print("踢出用户 \(userId) 失败: \(error.localizedDescription)")
184
+ }
185
+ }
186
+ }
187
+ }
188
+ ```
189
+
190
+ #### 4.2 设置/撤销管理员
191
+
192
+ 通过 `setAdministrator` 和 `revokeAdministrator` 接口可以管理用户的管理员身份。
193
+ ``` swift
194
+ extension AudienceManager {
195
+ /// 将用户设为管理员
196
+ func promoteToAdmin(userId: String) {
197
+ audienceStore.setAdministrator(userID: userId) { result in
198
+ if case .success = result {
199
+ print("成功将用户 \(userId) 设为管理员")
200
+ }
201
+ }
202
+ }
203
+
204
+ /// 撤销用户的管理员身份
205
+ func revokeAdmin(userId: String) {
206
+ audienceStore.revokeAdministrator(userID: userId) { result in
207
+ if case .success = result {
208
+ print("成功撤销用户 \(userId) 的管理员身份")
209
+ }
210
+ }
211
+ }
212
+ }
213
+ ```
214
+
215
+ ## 功能进阶
216
+
217
+ ### 在弹幕区展示观众入场欢迎语
218
+
219
+ 当有新观众进入直播间时,弹幕/聊天区域会在本地自动显示一条欢迎消息,例如:“欢迎 [用户昵称] 进入直播间”。
220
+
221
+ #### 实现方式
222
+
223
+ 我们通过订阅 `LiveAudienceStore` 的观众加入事件(`LiveAudienceEvent.onAudienceJoined`)来获取新观众加入的实时通知。一旦事件触发,我们便提取出新观众的昵称信息,然后立即调用 `BarrageStore` 的本地插入接口 `appendLocalTip`。
224
+ ``` swift
225
+ import Foundation
226
+ import AtomicXCore
227
+ import Combine
228
+
229
+ class LiveRoomManager {
230
+ private let liveId: String
231
+ private let audienceManager: AudienceManager
232
+ private let barrageManager: BarrageManager // 假设您已实现了弹幕文档中的BarrageManager
233
+ private var cancellables = Set<AnyCancellable>()
234
+
235
+ init(liveId: String) {
236
+ self.liveId = liveId
237
+ // 初始化两个核心管理器
238
+ self.audienceManager = AudienceManager(liveId: liveId)
239
+ self.barrageManager = BarrageManager(liveId: liveId)
240
+
241
+ // 设置联动
242
+ setupWelcomeMessageFlow()
243
+ }
244
+
245
+ private func setupWelcomeMessageFlow() {
246
+ // 1. 获取 LiveAudienceStore 的实例
247
+ let audienceStore = LiveAudienceStore.create(liveID: self.liveId)
248
+
249
+ // 2. 获取 BarrageStore 的实例 (得益于内部机制,这会是同一个实例)
250
+ let barrageStore = BarrageStore.create(liveID: self.liveId)
251
+
252
+ // 3. 订阅观众事件
253
+ audienceStore.liveAudienceEventPublisher
254
+ .receive(on: DispatchQueue.main)
255
+ .sink { event in
256
+ // 4. 只处理观众加入事件
257
+ guard case .onAudienceJoined(let newAudience) = event else {
258
+ return
259
+ }
260
+
261
+ // 5. 创建一条本地提示消息
262
+ var welcomeTip = Barrage()
263
+ welcomeTip.messageType = .text
264
+ welcomeTip.textContent = "欢迎 \(newAudience.userName) 进入直播间!"
265
+
266
+ // 6. 调用 BarrageStore 的接口将其插入弹幕列表
267
+ barrageStore.appendLocalTip(message: welcomeTip)
268
+ }
269
+ .store(in: &cancellables)
270
+ }
271
+ }
272
+ ```
273
+
274
+ ## API 文档
275
+
276
+ 关于 [LiveAudienceStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveaudiencestore) 及其相关类的所有公开接口、属性和方法的详细信息,请参阅随 [AtomicXCore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore) 框架的官方 API 文档。本文档使用到的相关 Store 如下:
277
+ <table>
278
+ <tr>
279
+ <td rowspan="1" colSpan="1" >Store/Component</td>
280
+
281
+ <td rowspan="1" colSpan="1" >功能描述</td>
282
+
283
+ <td rowspan="1" colSpan="1" >API 文档</td>
284
+ </tr>
285
+
286
+ <tr>
287
+ <td rowspan="1" colSpan="1" >LiveCoreView</td>
288
+
289
+ <td rowspan="1" colSpan="1" >直播视频流展示与交互的核心视图组件:负责视频流渲染和视图挂件处理,支持主播直播、观众连麦、主播连线等场景。</td>
290
+
291
+ <td rowspan="1" colSpan="1" >[API 文档](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/livecoreview)</td>
292
+ </tr>
293
+
294
+ <tr>
295
+ <td rowspan="1" colSpan="1" >LiveAudienceStore</td>
296
+
297
+ <td rowspan="1" colSpan="1" >观众管理:获取实时观众列表(ID / 名称 / 头像),统计观众数量,监听观众进出事件。</td>
298
+
299
+ <td rowspan="1" colSpan="1" >[API 文档](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveaudiencestore)</td>
300
+ </tr>
301
+
302
+ <tr>
303
+ <td rowspan="1" colSpan="1" >BarrageStore</td>
304
+
305
+ <td rowspan="1" colSpan="1" >弹幕功能:发送文本 / 自定义弹幕,维护弹幕列表,实时监听弹幕状态。</td>
306
+
307
+ <td rowspan="1" colSpan="1" >[API 文档](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestore)</td>
308
+ </tr>
309
+ </table>
310
+
311
+
312
+ ## 常见问题
313
+
314
+ ### `LiveAudienceState` 中的在线人数(`audienceCount`)是如何更新的?时机和频率是怎样的?
315
+
316
+ `audienceCount` 的更新并非总是实时的,其机制如下:
317
+ - **主动进出房间**:当用户主动加入或正常退出直播间时,在线人数的变更通知会即时触发。您会很快在 `LiveAudienceState` 中观察到 `audienceCount` 的变化。
318
+
319
+ - **异常掉线**:当用户因网络问题、应用崩溃等原因异常掉线时,系统需要通过心跳机制来判断其真实状态。只有当该用户连续 90 秒没有心跳后,系统才会判定其为离线,并触发人数变更通知。
320
+
321
+ - **更新机制与频率控制:**
322
+
323
+ - 无论是即时触发还是延迟触发,所有的人数变更通知都是以消息的形式在房间内广播的。
324
+
325
+ - 房间内每秒的消息总量有上限,单房间消息频控是**每秒 40 条消息**。
326
+
327
+ - **关键点:**在“弹幕风暴”或礼物刷屏等消息流量极高的场景下,如果房间内的消息速率超过了 40条/秒 的阈值,为了保证核心消息(例如弹幕)的送达,**人数变更的消息可能会被频控策略丢弃**。
328
+
329
+
330
+ **这对开发者意味着什么?**
331
+
332
+
333
+ `audienceCount` 是一个非常接近实时的**高精度估算值**,但在极端高并发场景下,它可能存在短暂的延迟或数据丢失。因此,我们建议您将其用于 **UI 展示**,而不应作为计费、统计等需要绝对精准场景的唯一依据。
334
+
335
+