rsocket-java
rsocket-java copied to clipboard
Java implementation of RSocket
When the client is closed, the rsocket server does not receive the cancellation event and ongoing flux subscription still continues which leads to data loss. How to cancel the ongoing...
I want to ask question here as there is the similar question in StackOverFlow which is not answered (https://stackoverflow.com/questions/67898403/using-rsocket-payloaddecoder-zero-copy-correctly). So my question is when I use `.payloadDecoder(PayloadDecoder.ZERO_COPY)` where and how...
Not knowing if this was a Spring Boot, Spring Security, RSocket, or Netty issue, I originally filed this against Spring Boot as spring-projects/spring-boot#34853. They forwarded me here given that exclusively...
closes #988 Signed-off-by: Oleh Dokuka Signed-off-by: Oleh Dokuka
support netty boringssl aarch_64 ### Motivation: Netty boringssl is available on arm64 (aarch_64) Let's use the proper classifier. ### Modifications: update build.gradle ### Result: Correct artifact is observed on MacOS...
I use the Spring framework to implement data reception Kotlin ```java @MessageMapping("/upload") fun upload(@Payload fileData: ByteArray?): Mono { println("========= OK") println("========= OK "+ fileData!!.size) val uploadFile = File("/Users/Downloads/uploaded_file.png") // return...
Currently, the only context a Lease seems to have access to is the connection through the `TrackingLeaseSender` interface. This makes sense, but I have a use case where I would...
Our application needs to be able to store the client address of a client in a database for any auditable action. When those actions are initiated via an RSocket request,...
Assume there are two connections that both transmit metadata upon establishment. In SocketAcceptorInterceptor, metadata from one connection can be accessed from the other connection. However, I want to ensure that...
## Expected Behavior `requestStream` should continue serving messages infinitely. ## Actual Behavior After `Integer.MAX_VALUE` messages, no more `requestN` frames are sent by the client, and the server stops sending messages....