This repository was archived by the owner on Feb 24, 2026. It is now read-only.
Open
Conversation
…g the “list selector” metaphor known from GET and POST requests
…server side implementation requirements
…ubscribe on a list and get updates on each element
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Add a feature that allows automatic subscription for all elements of a list a client subscribes to. This feature reduces the number of subscribe messages for n+1 to 1. This is extremely helpful for larger lists and correpsoning list views, which might have certain performance requirements.
E.G. a list that holds 100 items and is displayed in a carrousel view would need 101 subscription messages in the legacy protocol versions, while with the new approach it would just take 1 subscription message. All server side emitted events are of course still 101, if everything changes.
Anyway, the subscription latency is reduced drastically.