-
Notifications
You must be signed in to change notification settings - Fork 20
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
Comments
yes. the trick is to record only what remote definitely said they had. 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. |
Thanks. I guess we leave this open until it’s in the readme? |
yes good plan
…On 5/3/19, Henry ***@***.***> wrote:
Thanks. I guess we leave this open until it’s in the readme?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/dominictarr/epidemic-broadcast-trees/issues/26#issuecomment-488938456
|
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?
The text was updated successfully, but these errors were encountered: