feat: introduce dialog snapshot hooks#83
Merged
yeoleobun merged 1 commit intoJan 19, 2026
Conversation
6bd8cbc to
21324a3
Compare
Collaborator
|
Thanks your contribution! Relate to #65 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change adds a dialog snapshot API and the ability to restore CONFIRMED dialogs from it.
The snapshot provides a stable, serializable view of a dialog (IDs, tags, contacts, route set, CSeqs) that can be safely persisted outside the process.
Restore is intentionally limited to CONFIRMED dialogs only.
Non-confirmed dialogs are skipped because their signaling and transaction state cannot be safely resumed after a restart.
This allows applications to survive restarts and continue working with already-established dialogs without losing dialog identity and routing information.