Oleg Yukhnevich

Hi, thanks for report! This is something what could be provided (rsocket-java has access to `SocketAddress` from connection for example). But this way it will not work for rsocket-kotlin as...

Notes here: * coroutines only support WasmJs target for now * ktor support WasmJs only in 3.0.0-beta So proper support will be available only after ktor 3.0 will be released.

Hey! Thx for the report, though it's hard to understand what is the issue on current moment. Can you please add frame logging on client or server side (via rsocket-java/rsocket-kotlin...

Good to hear that it solves issue on your side! Overall using `maxFragmentSize` should not cause any issues, but overall - stick with defaults unless needed :) Example in README...

Looks like the same issue as #211. So I think it's ktor side As for workaround is to provide `CoroutineExceptionHandler` to server instance via `scope` or `parentCoroutineContext` which goes directly...

related: #226 May be it will be possible to fix it in `rsocket-kotlin` in similar way during refactoring of transports

From what I've checked, looks like it's not possible to add exception handler for websocket session... Need to create an issue on ktor side for this (?). Still it's possible...

will be fixed on ktor side here: https://youtrack.jetbrains.com/issue/KTOR-5016/Channel-was-closed-exception-in-WebSocket-during-normal-use

Change should be a little bigger. We need to make receive result nullable and handle it where it's called. This will affect all transport implementations and not only websocket. Also...

Sorry for the delay. Focus switched on new transport API. I've tried to create a quick fix, but it's really degrade stability and expected behavior of current transport implementation and...