feat: SSE AgentSignals for agent events#145
Open
kentbull wants to merge 1 commit into
Open
Conversation
Signed-off-by: Kent Bull <kent@kentbull.com>
This was referenced May 6, 2026
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
1 participant
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 adds the Signify client counterpart to KERIA's SSE AgentSignals, broadcaster, SSE endpoint, and SSE iterable. This supports one or more Signify clients connecting to a given server Agent to get unique server sent events streams per SignifyClient controller instance.
This is in preparation for future event driven features including the did:webs integration, among others. The SSE event stream is also a convenient way for clients to switch from long-polling to observing events sent from an agent. Long-polling is still be supported as a fallback, though this allows SSE to be the default future communication pathway from the agent to a client. This will significantly help with both bandwidth and performance on highly used Agency servers.
Currently this PR pins to a kentbull/keria repo Git SHA since the code is not yet merged to KERIA. Once PR WebOfTrust/keria#435 is merged then this PR will change to point to WebOfTrust/keria
main.