kcp-go icon indicating copy to clipboard operation
kcp-go copied to clipboard

A Crypto-Secure, Production-Grade Reliable-UDP Library for golang with FEC

Results 64 kcp-go issues
Sort by recently updated
recently updated
newest added

如果客户端发送的pps较少,而服务端发送的pps很多时。 其实客户端不需要开启fec,只需要服务端开启fec就好了。 是不是可以这么理解?

我试了kcp-cpp kcpp之类的。或多或少都有些问题。

Hello, I am experimenting with kcp-go and I guess I am doing something wrong. I want to send a bigger amount of data through kcp connection... but it's weirdly slow?...

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

I have taken the echo example, split it into 2 components: ### client.go: ``` package main import ( "crypto/sha1" "io" "log" "time" "github.com/xtaci/kcp-go/v5" "golang.org/x/crypto/pbkdf2" ) func main() { client() }...

I have implemented the server and client using the kcp-go framework. The server sent a data packet larger than 1500 bytes. I expected the server to split this packet, and...

当UDPSession调用read和write后,重新设置超时时间不会生效。查看sess.go,修改超时时间会调用:notifyReadEvent(),实际上是往s.chReadEvent写一个空结构体。在Read函数里245行,当收到

发现下面的代码在服务端重启时,客户端上报的sn和服务端的rcv_nxt不一致,导致服务端恢复的连接无法read客户端数据。 在代码增加恢复服务端rcv_nxt是否可行呢?(下面代码注释部分) https://github.com/xtaci/kcp-go/blob/e026777b9cb8afa9ce8a963f3e54ffccaf03f6a1/sess.go#L838C3-L847C4 ``` golang if s == nil && convRecovered { // new session if len(l.chAccepts) < cap(l.chAccepts) { // do not let the new sessions overwhelm accept queue...