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

Request skipping #26

Open
cryptix opened this issue Apr 30, 2019 · 3 comments
Open

Request skipping #26

cryptix opened this issue Apr 30, 2019 · 3 comments

Comments

@cryptix
Copy link
Member

cryptix commented Apr 30, 2019

I found a couple of links and mentions about this but I couldn't find a clear explanation altough it sounds simple.. Is it just leaving out unchanged feed in the note/vector clock updates?

@dominictarr
Copy link
Contributor

yes. the trick is to record only what remote definitely said they had.
If you request from A5 and I send you A6 and A7, I record that you definitely have A5. (I don't know 100% that you received 7) next time we connect, I check my records, and it says you definitely have A5, I check what I have (A7) it's different, so I mention that.

This time, you have A7 too, cool. I record that. next time, I check, it says A7, that's what I have. so I leave it out. If you have a newer message for A, you'll mention it, then i'll say I have A7, and you'll send it.

Also, if you are not interested in a feed, you say -1 and I record that you don't want that feed. If you change your mind later, you have to mention it.

@cryptix
Copy link
Member Author

cryptix commented May 3, 2019

Thanks. I guess we leave this open until it’s in the readme?

@dominictarr
Copy link
Contributor

dominictarr commented May 3, 2019 via email

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

2 participants