Timeline for Need to test for equality on vector clocks
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 4, 2020 at 13:57 | audit | Suggested edits | |||
| Feb 4, 2020 at 13:58 | |||||
| Jan 13, 2020 at 12:15 | vote | accept | dan1st | ||
| Jan 13, 2020 at 12:14 | answer | added | Ewan | timeline score: 1 | |
| Jan 13, 2020 at 12:10 | comment | added | dan1st | This is the whole point. I believe that there can not be every timestamp the same because it every process does only increment it's own timestamp only on actions and messages. | |
| Jan 13, 2020 at 12:08 | comment | added | Ewan | @dan1st I understand that, what im sayign is that if you take two arbitrary messages, you might have chosen the exact same one twice, in which case the timestamps would be exactly the same | |
| Jan 13, 2020 at 12:05 | review | Close votes | |||
| Jan 30, 2020 at 3:05 | |||||
| Jan 13, 2020 at 12:05 | comment | added | dan1st | @Ewan These are logical timestamps. Every process in a distributed system has it's own logical timestamp that is just a number. It increments only it's own logical timestamp on every process. | |
| Jan 13, 2020 at 12:03 | comment | added | Ewan | trivally they are equal if you are comparing the same timestamp | |
| Jan 13, 2020 at 11:59 | comment | added | dan1st | Every message sends a vector(array) of "timestamps". But these timestamps are only logical timestamp. Every process increments it's own timestamp on each action/transmission and it doesn't have to do anything with real timestamps. | |
| Jan 13, 2020 at 11:57 | history | edited | dan1st | CC BY-SA 4.0 |
link
|
| Jan 13, 2020 at 11:57 | comment | added | dan1st | These are arrays. 2 belonging elements are elements with the same index. | |
| Jan 13, 2020 at 11:40 | review | First posts | |||
| Jan 15, 2020 at 14:59 | |||||
| Jan 13, 2020 at 11:39 | history | asked | dan1st | CC BY-SA 4.0 |