is there any good pattern to do the handling of websocket messages outside the

webSocket

block? I’m trying to do something like:

webSocket("/ws") {
    val webSocketTransport = WebSocketTransport(this)
    eventHandler.newWebSocketConnected(webSocketTransport)
}

where the

WebSocketTransport

launches a coroutine to read the incoming messages:

scope.launch {
    for (msg in webSocketSession.incoming) {
        ...
    }
}

but when I try this, the websocket disconnects immediately, because it looks like it’s implemented in a way to close as soon as the passed

handler

returns. Is there any good pattern move that logic out? I did it one way where I added another channel, and the webSocket handler read messages and wrote them to that channel, and WebSocketTransport read from that channel, but was hoping to avoid having to create the intermediary.

if

scope

is the current scope or a child then it will all work out

Ah great…so something like create a child scope and pass that to

WebSocketTransport

?

yes, that will work, or refactor it to avoid the launch altogether

I now have:

webSocket("/ws") {
            coroutineScope {
                val webSocketTransport = WebSocketTransport(this@webSocket, this@coroutineScope)
                handler.newWebSocketConnection(sessionId, webSocketTransport)
            }
        }

which seems to be working right…does that look reasonable?

so that's one way to do it, although

this@webSocket

should already implement

CoroutineScope

Ah! That’s even better

hmm it doesn't? I'm not sure why that would be… but I guess an explicit

coroutineScope {}

works

from what i can tell it doesn’t. i can stick with the coroutineScope method…bit uglier but it seems to work.

it does create a child scope, it must be something ktor is doing with the pipeline

ok

you can use

client.webSocketSession(request)

if you need manual control over closing

@Rustam Siniukov what’s “client” there/what scope is it available in? is that something available inside

routing

?

Sorry, my fault. It’s a client API, not server.

Maybe, this answer helps you.