Does this look like a good way to manage a session interaction: ``` fun dispatch(event: ChatSessi...

# coroutines

[Daniel Pitts]

Does this look like a good way to manage a session interaction:

fun dispatch(event: ChatSessionClientEvent): Flow<ChatSessionServerEvent> {
        return flow {
            when (event) {
                is MakeChoice -> makeChoice(event)
                ReloadSettings -> reloadSettings()
                is RequestChatState -> requestChatState(event)
                ResetSettings -> resetSettings()
                SaveSettings -> saveSettings()
                is SetTools -> setTools(event)
                is ToolCallResults -> toolCallResults(event)
                is UpdateSettings -> updateSettings(event)
                is UserMessage -> userMessage(event)
            }
        }.shareIn(this, SharingStarted.WhileSubscribed())
    }

Where the event handlers will emit ChatSessionServerEvent instances.

[ephemient]

creating a new flow with a single element each time the function is called seems unlikely to be useful

[Daniel Pitts]

It isn’t a single element, multiple events can be emitted from a single command.

[Daniel Pitts]

In any case, I reorganized this to use two Channels instead. One for incoming commands, the other for outgoing state updates.