How to stop sending SSE to disconnected client?

[SuperCuber]

I have the following simple code:

#[get("/listen")]
async fn handle_listen(mut shutdown: Shutdown) -> EventStream![] {
    EventStream! {
            let mut interval = tokio::time::interval(tokio::time::Duration::from_secs(1));
            loop {
                select! {
                    _ = interval.tick() => {
                        println!("Sending ping");
                        yield Event::json(&"ping");
                    }
                    _ = &mut shutdown => {
                        break;
                    }
                }
            }
        }
}

And I have in my client a simple loop that sets up an event listener. The events arrive properly, but when I call eventSource.close() in the client the server keeps printing that the pings are being sent, despite the client no longer listening to them.

How should I detect this and stop the useless processing on the server side?

[SuperCuber]

Did you mean to answer #2966 ?

[SergioBenitez]

None of this is true. You can run as many instances of Rocket in a single process as you want: all of the things like config, state, and async execution are owned by each individual Rocket instance: there's no sharing. The only sharing would be at the tokio / async executor level, but this is a general Rust problem, not something Rocket can address.

[SuperCuber]

@SergioBenitez am I crazy or are all these comments completely off topic for this thread and don't relate to the question? To the point where I'm suspecting @pranavmanglik to be a bot? I realize your reply is an effect of Cunningham's Law but I feel like I'm missing something 😂

[SergioBenitez]

Yeah, no idea what's going on! I'll collapse them for now and do something more drastic should this be recurring.