feat(notifications): Add WebSocket and Server-Sent Event channels#162
Draft
laurensdeb wants to merge 1 commit into
Draft
feat(notifications): Add WebSocket and Server-Sent Event channels#162laurensdeb wants to merge 1 commit into
laurensdeb wants to merge 1 commit into
Conversation
Introduce client-server streaming notification channels: - WebSocket: persistent bidirectional connection for real-time events - Server-Sent Events (EventSource): persistent HTTP stream for real-time events Both channels use capability URLs for connection establishment and share the common notification envelope defined in the base specification.
Contributor
Author
|
See preview |
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
2 participants
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 is a class 4 change to the protocol. It will need discussion and a WG vote before merging.
This PR adds client-server streaming notification channels on top of the base notifications specification (#161):
Both channels use capability URLs for connection establishment and share the common notification envelope defined in the base specification.
Depends on #161
Preview | Diff