Executive Summary
A new concurrency option has been introduced to the Chat SDK's `Chat` class, providing developers with explicit control over how the system handles new messages that arrive while a previous message is still being processed. This update offers four distinct strategies to manage message flow, from dropping new messages to queueing them for sequential handling. The feature is designed to help developers build more robust and predictable chat applications.
Key Takeaways
* New Feature: A `concurrency` configuration option is now available for the `Chat` class.
* Primary Function: It defines the behavior when a new message arrives before the handler for a previous message has finished.
* Four Available Strategies:
* `drop` (Default): Discards any new messages that arrive during processing.
* `queue`: Places new messages in a configurable queue to be processed sequentially.
* `debounce`: Waits for a pause in the conversation and then processes only the final message from a burst.
* `concurrent`: Processes every incoming message immediately, without waiting or locking.
* Availability: The feature is available now.
Strategic Importance
This update gives developers essential tools to manage high-volume message traffic, preventing race conditions and ensuring chat applications behave predictably under load.