4 ms·
The context here is events originated by a single actor, so wallclock is much more reasonable than in the general distributed system case. You might still be wo
by nhaehnle 11y ago
The context here is events originated by a single actor, so wallclock is much more reasonable than in the general distributed system case. You might still be worried about the user accessing your system simultaneously from multiple devices, so a randomly generated ID is probably still useful.
- zAy0LfpBZLC8mAC 11y agoFirst, it's usually impossible to tell actors apart, so it's not particularly useful to build an algorithm that depends on doing so. Second, while the actor might be the same, the time source usually is not, so it still doesn't help you. Third, if actor and time source are indeed the same, you really are using a counter, the fact that it's correlated with wallclock time is coincidental.
- philsnow 11y agoPiling on, even if the actor and time source are the same, you have to be really careful about how your use "wall clock time", because if you're just asking the OS what time it is, a lot of platforms allow the clock to move backwards, not move, etc.