We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
我的使用场景比较奇葩,推流多,播放少。 搭建多个源节点,使用Haproxy来负载,用于分散在线的流,而播放时,则走边缘节点,或者是直接走源节点。
如果使用lal的话,应该我自己实现一个程序,当从边缘节点拉流时,我查询到在哪个源节点,然后去拉流。
能否实现RTMP 302重定向的功能,我直接将重定向后的流地址下发给播放端去重定向。
不知拉流与RTMP 302重定向,哪种的播放等待时间能更短一些
The text was updated successfully, but these errors were encountered:
看你播放端到源节点的链路 vs 边缘节点到源节点的链路 哪个更好, 理论上第2个是由你控制的,应该更好些,
Sorry, something went wrong.
No branches or pull requests
我的使用场景比较奇葩,推流多,播放少。
搭建多个源节点,使用Haproxy来负载,用于分散在线的流,而播放时,则走边缘节点,或者是直接走源节点。
如果使用lal的话,应该我自己实现一个程序,当从边缘节点拉流时,我查询到在哪个源节点,然后去拉流。
能否实现RTMP 302重定向的功能,我直接将重定向后的流地址下发给播放端去重定向。
不知拉流与RTMP 302重定向,哪种的播放等待时间能更短一些
The text was updated successfully, but these errors were encountered: