rsocket-kotlin
rsocket-kotlin copied to clipboard
rsocket
RSocket Kotlin multi-platform implementation
When opening connections through the ktor client API, it looks like there's no good way to customize the setup metadata for each connection. It can only be set once for...
Hello! No output to log of io.rsocket on jvm What is the idiomatic way to organize logging for logback jvm? I looked at current implementations, and did it by analogy...
I have encountered a problem with reconnecting from the client side. The reconnectable block is triggered only before the first successful connection. https://github.com/rsocket/rsocket-kotlin/pull/308 Here is a minimal example that reproduces...
I have encountered a problem with reconnecting from the client side. The reconnectable block is triggered only before the first successful connection. Here is a minimal example that reproduces the...
Main changes: * rename to `RSocketMimeType` * move to root package * use nested classes POC API: ```kotlin public sealed interface RSocketMimeType { public sealed interface WithName : RSocketMimeType {...
* current RSocketError API is not very useful * custom Errors handling should be introduced, so that it's possible to transform exception with custom error codes in specific exception *...
To be able to easier support features like Lease, accessing connection state or accessing connection information (TCP address or web socket session headers) we need to redesign how we connect...
Currently, [RequestStrategy](https://github.com/rsocket/rsocket-kotlin/blob/58ca7978603d75d380bf4568dbb3264a82afcf99/rsocket-core/src/commonMain/kotlin/io/rsocket/kotlin/RequestStrategy.kt#L31) API is very bad designed. While it allows to configure how to request the data, the API is hard to use and not intuitive. It need to be...
Is there an easy way to know the current RSocket instance by `path` (url or any other tag like id or hash) when processing errors in the `reconnectable {...}` block?...
RSocket protocol v2 has small changes which are incompatible with v1: * https://github.com/rsocket/rsocket/pull/312 * https://github.com/rsocket/rsocket/pull/311 Investigate what is needed to support those and how to support both v1 and v2:...