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
撇开kcptun只能代理tcp这个差别。 kcptun我理解qos核心靠arq+fec功能,UDPspeeder就没有arq吧,只有个fec,请教两个问题: 1、UDPspeeder和kcptun的fec功能差别在哪呢?UDPspeeder的fec功能会更好吗? 2、当UDPspeeder的fec冗余都恢复不了包时,怎么办,就确实丢了吧,还是会有nack或者arq来确保重传得到包呢?
The text was updated successfully, but these errors were encountered:
当UDPspeeder的fec冗余都恢复不了包时,怎么办,就确实丢了吧,还是会有nack或者arq来确保重传得到包呢?
没有nack/arq,只有fec。
如果需要nack/arq ,在上层做。udpspeeder设计上不负责做这个。
Sorry, something went wrong.
撇开kcptun只能代理tcp这个差别。 UDPspeeder和kcptun的fec功能差别在哪呢?
没法强行撇开
kcptun只能转发tcp
UDPspeeder是转发udp的
应用场景就不同
UDPspeeder的fec功能会更好吗?
如果一定要这么问:
No branches or pull requests
撇开kcptun只能代理tcp这个差别。
kcptun我理解qos核心靠arq+fec功能,UDPspeeder就没有arq吧,只有个fec,请教两个问题:
1、UDPspeeder和kcptun的fec功能差别在哪呢?UDPspeeder的fec功能会更好吗?
2、当UDPspeeder的fec冗余都恢复不了包时,怎么办,就确实丢了吧,还是会有nack或者arq来确保重传得到包呢?
The text was updated successfully, but these errors were encountered: