confused about the websocket/chat example model

[yatesco]

Does the web socket loop persist as long as the client is connected, which I can't believe it does do to resource drainage. If not, how do I associate a "user" (e.g. their session id/cookie) with their particular socket?

Do I split the socket on_connect and then shove the write site into a map? I guess it needs to be a weak reference in case the client disappears?

I wasn't kidding about the newbie section ;-).

[davidpdrsn]

Does the chat example help https://github.com/tokio-rs/axum/blob/main/examples/chat/src/main.rs?

[davidpdrsn]

The function runs until it returns 😅 it's passed directly to tokio::spawn so its really up to you. Could be when the client disconnects (ie receiving a message fails) but you're free to do other stuff afterwards, or return early if you want.

How exactly you want to manage the connections and whatnot I don't have recommendations for. A HashMap and some tokio mpsc channels is probably a good way to start.

[yatesco]

right :-), so just to be clear - the loop at line 108:

    // This task will receive messages from client and send them to broadcast subscribers.
    let mut recv_task = tokio::spawn(async move {
        while let Some(Ok(Message::Text(text))) = receiver.next().await {
            // Add username before message.
            let _ = tx.send(format!("{}: {}", name, text));
        }
    });

will run for a long time until the client disconnects, if I'm reading this right?

[davidpdrsn]

Yep that's correct!

[yatesco]

thanks - I knew I was overthinking it ;-)

[davidpdrsn]

No worries. Happy to help 😊