Skip to content
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

Proposal: further constraining the EventSource view #34

Open
pietercolpaert opened this issue Apr 14, 2023 · 1 comment
Open

Proposal: further constraining the EventSource view #34

pietercolpaert opened this issue Apr 14, 2023 · 1 comment

Comments

@pietercolpaert
Copy link
Member

Current proposal would be that the EventSource view must have relations with tree:path equal to the ldes:timestampPath

@pietercolpaert
Copy link
Member Author

pietercolpaert commented Sep 21, 2023

Revisiting what I said here:

An ldes:EventSource can only be added on a view that:

  • has in-order updates: the ldes:timestampPath will only increase
  • and therefore the state that can be kept by a client for doing sync/repl, can be done based on a timestamp + the members at that timestamp that were already visited.
  • promises a best-effort to keep the repl and sync process as efficient as possible

It’s thus up to the publisher to decide whether that means indeed that the ldes:timestampPath is being used in the relations, or that a composed fragmentation is done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant