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

An unavailable document may just not be found yet #293

Open
acurrieclark opened this issue Feb 9, 2024 · 0 comments
Open

An unavailable document may just not be found yet #293

acurrieclark opened this issue Feb 9, 2024 · 0 comments

Comments

@acurrieclark
Copy link
Collaborator

Consider the following:

  1. 2 peers, Alice, Bob. Bob has a share policy of false.
  2. Alice tries to find a document which neither of them has. It isn't available, so that gets marked as unavailable on both peers.
  3. Bob now gets that document, but their share policy means that it doesn't get shared immediately with Alice.
  4. If Alice tries to find the document again, there will be an immediate unavailable event fired, but at the same time it will sync it from Bob and then the document will resolve.

My question is, should we remove the immediate unavailable event until another sync attempt has been made?

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