上下线消息#
如未设置回调事件,请先创建回调事件才可以正常回调:回调事件创建为了能够感知用户在直播间上下线状态,方便后续业务逻辑处理,微吼提供上下线消息异步回调能力;回调内容#
上线消息#
{
"client": "android",
"context": {
"avatar": "",
"device_status": 1,
"device_type": 3,
"nickname": "马小兰",
"pv": 1237,
"role_name": 2
},
"email": "eaaa32df52d0@xxx.com",
"login_ip": "127.0.0.1",
"method_id": 20,
"pv": 49,
"refer": "vhall",
"sender_id": "170319839",
"service_type": "service_online",
"socket_id": "XEMh1E8Noiqm9",
"time": 1736488036,
"type": "Join",
"uv": 49,
"webinar_id": 677528421,
"webinar_user_id": 167729650,
"signature":"xxxxxxxxxxxx"
}
下线消息#
{
"client": "ios",
"context": {
"avatar": "",
"device_status": 1,
"device_type": 3,
"nickname": "聂帅",
"pv": 5,
"role_name": 2
},
"email": "82530871eade@xxx.com",
"login_ip": "127.0.0.1",
"method_id": 20,
"pv": 0,
"refer": "vhall",
"sender_id": "181960229",
"service_type": "service_online",
"socket_id": "9xvLVG8ha3egECQyws6M",
"time": 1736488160,
"type": "Leave",
"uv": 0,
"webinar_id": 514264960,
"webinar_user_id": 170774339,
"signature":"xxxxxxxxxxxx"
}
上下线消息的通知不保证严格的时间顺序, 在进行业务处理时不可按照消息接收到的时间顺序来进行业务处理;举例: 微吼通知同一用户的上线消息和下线消息,由于网络原因或者调用失败等异常情况,接收端有可能会首先接收到下线消息,后收到上线消息.
上下线消息,随着版本迭代,可能出现字段增加的情况, 请在实现参数接收或者验证签名时,不要对数据接收模型与现有消息格式进行强绑定