-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to specifiy subscription scope? #269
Comments
D = A + B + C + E anyway? I'm guessing E is most practical as it effectively generalizes A and C but is more flexible, and probably easier to get to perform. |
How does D include A? With D, I had to subscribe to every partition to have the same result as A. |
I would suggest C + D + E (where C is a special case of E) |
+1 |
If we subscribe to a node, which kind of deltas do we get?
|
From Modelix' experience, it's very hard to maintain a consistent state of a partially subscribed model on the client. There's also a redundancy in your implementation: Both your scope description and the actual code that processes the model need to know about the required scope. |
When a delta protocol client connects to the repository, it might want to define what updates it cares for.
Potential scopes
A Whole repo
Pro:
Con:
B All nodes of concept X
Pro:
Con:
C Partitions
Pro:
Con:
D Any node
Pro:
Con:
E Any node with optional
depth
Same as D, but the client can optionally specify a
depth
parameter (as in bulk retrieve).Pro:
Con:
Working assuption: D
Any node can be defined as scope. Scope includes that node and all descendants(children + annotations). Client can subscribe to several nodes.
The text was updated successfully, but these errors were encountered: