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
当前策略:目前KCP类似与TCP,总是可靠传输每个数据包,但在网络丢包、延迟大的情况下,会导致发送端延迟越来越大,直到占满发送buffer后,阻塞发送端。
期望策略:当接收端检测到丢包后,尽量触发重传,但当重传次数或等待时间超过某个阈值后,将放弃该包,继续处理下个SN的包
应用场景:实时音视频传输,该场景下实时性的需求大于可靠性(参考方案:webrtc中基于rtp/rtcp的jitter buffer + nack + fec)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
当前策略:目前KCP类似与TCP,总是可靠传输每个数据包,但在网络丢包、延迟大的情况下,会导致发送端延迟越来越大,直到占满发送buffer后,阻塞发送端。
期望策略:当接收端检测到丢包后,尽量触发重传,但当重传次数或等待时间超过某个阈值后,将放弃该包,继续处理下个SN的包
应用场景:实时音视频传输,该场景下实时性的需求大于可靠性(参考方案:webrtc中基于rtp/rtcp的jitter buffer + nack + fec)
The text was updated successfully, but these errors were encountered: