Repository navigation
feat(jet1090): add /stream endpoint for live decoded messages - #538
Merged
Merged
Conversation
# Conflicts: # crates/jet1090/src/main.rs
Owner
|
Thank you! |
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.
Closes #536.
Adds a
/streamroute to the web API that pushes every decoded message as server-sent events, one message per event, in the same JSON as the.jsonloutput and the Redis feed. Any browser can read it withEventSource. axum already ships SSE, so nothing new is pulled in.It is a plain output next to Redis and
.jsonl. It does not filter per client and keeps no state about who is listening. The global--df-filterand--aircraft-filterapply before anything reaches the stream. Messages go through a broadcast channel, so the decoder never waits on a client. A client that falls more than 4096 messages behind is moved to the live edge of the feed and misses what happened in between, instead of replaying a stale backlog.Tested against two live Beast feeds, with two concurrent clients and with a client falling behind.