-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Transition to Ready state after all initial messages are received
Previously, we transitioned to Ready state as soon as we received the first message (since that meant that communication with the broker had been established). Now, we transition to Readying state once we receive the first message, and only transition to Ready state once we have received all of the initial messages triggered by the first KeepAlive. This ensures that data is in a coherent state when Ready. Also, construct timers as children of the producer, to ensure that timer events are serviced on the producer's thread.
- Loading branch information
Showing
2 changed files
with
45 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters