How to support server side events (sse)

I’m experimenting with SSE, and run into the problem that the server keeps on sending data even when the client is gone (or closes the connection). This is problematic, because over time, these zombie tasks will pile up. The same situation would occur with long-polling.

So at first I spawned a task that will call receive() until it gets "http.disconnect" and then cancels the task corresponding to the request (the one that sends messages to the client).

But this seems rather awkward, so I took a look at send(), and saw that this line means that my coroutine happily keeps sending data … into the void, forever.

Would it make sense to replace that return with a RuntimeError? Or is there another solution that I overlooked?

[almarklein]

Ping @florimondmanca

Already contributed 😉

[almarklein]

I recently found the time to look into this again, and added proper support for SSE to Asgineer. As for my original question, the pattern to follow is to let a task receive, as to detect the client from disconnecting. I now see how this is better 😃

For those interested: in Asgineer I added support to be able to sleep the connection: until the connection closes, a timeout expires, or it is woken up. This allows using SSE (and e.g. long-polling) in various ways.

Anyway, this can be closed.