Hi, I have something like this: ```fun serviceSseRequest(sseEmitter: SseEmitter) { val liveOutp...

# coroutines

[Czar]

Hi, I have something like this:

fun serviceSseRequest(sseEmitter: SseEmitter) {
  
  val liveOutput: Channel<String> = doSomethingInBackground()
  
  liveOutput.consumeAsFlow().collect { sseEmitter.emitServerSideEvent(it) }
}

How do I determine that there won't be any more messages in the channel? Maybe there is some other component that I can use instead of the channel here?

[araqnid]

doSomethingInBackground() should presumably close the send side of the channel (just close())

[Czar]

if I close it in the background job I face situation where not all messages were consumed by the slow reader.

[Dennis]

A Channel is Rendezvous by default, right? Your producer will be slowed down by your consumer.

[Dennis]

https://kotlinlang.org/docs/reference/coroutines/channels.html#channel-basics

[Dennis]

Conceptually, a close is like sending a special close token to the channel. The iteration stops as soon as this close token is received, so there is a guarantee that all previously sent elements before the close are received

[bdawg.io]

Make sure it's being told to close close() and not cancel() since that would indeed cause your consumer not to receive all the values

[Czar]

Thanks, I'll look into these suggestions