-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When the same client is streaming, the client_id for on_dvr callback is different from the other callbacks. #458
Comments
Can you provide more information? I didn't understand much.
|
srs2 http_hook http回调我的程序的时候,同一个客户端的情况下 on_connect on_publish 等 传过来的client_id的值都是一样的 只有 on_dvr 传过来的client_id 和其他几个 callback不一样 |
Oh, I understand now. It's because the DVR is an asynchronous request that cannot be blocked, while the others are synchronous requests. Asynchronous requests are all opened in new threads, which causes the IDs to be different. This can be considered a bug.
|
Already fixed.
|
on_dvr
|
牛逼 |
awesome
|
The client_id for on_dvr callback is different from other callbacks when streaming with srs2.
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: