Jeffsky
Jeffsky
I think that should be an independent project(eg: rsocket-plugin-grpc-go) and we have [rsocket-rpc-go](https://github.com/rsocket/rsocket-rpc-go/) already. Anyway, we should wait for L37 proposal to be accepted in GRPC. Then we can create...
Sorry for the late reply, I will check the timeout logic once I have time.
The current `Flux Processor` doesn't support Context API, it will be supported in the near future.
Thanks for report! It seems a bug. When sending a large payload, it will be split to some little frames first, the original releasable payload resource will be released after...
Please use v0.8.4 and feel free if you have any question. 😃
Try remove `Fragment(1024).Resume()` from server, I think it is not necessary here. Then you can open the debug level log, the SDK will print each binary payload, and you can...
By the way, use `logger.SetLevel(logger.DebugLevel)` to open it.
To be honest, I think the Java implementation is much more stable than the Go, so let's check the Go SDK first. 😄
Lease 有些问题，之前只实现了发送lease的逻辑，后面需要重写下，支持rate limit。
首先，Resume功能预置的存储是在内存里的，所以这里断开的情况只能支持网络挂掉，server和client进程不能挂。`WithServerResumeSessionDuration`意思是server仅维持一定时间的session，超过这个时间后会被剔除，无法维持断点续连。 参考`rsocket_test.go`里的`TestResume`。另外这个功能不建议打开，会加重server的压力。