This article is within the scope of WikiProject Time, a collaborative effort to improve the coverage of Time on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.TimeWikipedia:WikiProject TimeTemplate:WikiProject TimeTime articles
This article is within the scope of WikiProject Computer science, a collaborative effort to improve the coverage of Computer science related articles on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Computer scienceWikipedia:WikiProject Computer scienceTemplate:WikiProject Computer scienceComputer science articles
This article has been given a rating which conflicts with the project-independent quality rating in the banner shell. Please resolve this conflict if possible.
[Lam78] L. Lamport: Time, Clocks, and the Ordering of Events in a Distributed System, Communications of the ACM 21(7), pp.558-565, 1978.
)
I've added a new section, Implications: where I tried to explain what a Lamport clock actually means. I did this by reading Lamport's paper, so I hope I didn't make a mistake. Nadalle (talk) 06:31, 23 November 2008 (UTC)[reply]
I didn't like the explanation that stated two events could not have the same timestamp. This supposes a total order on the system in question. I changed this to refelect that a partial order must be maintained and prefixed that by saying two events cannot occur simultaneously on any single entity. Please comment on this explanation if you wish to change it, thanks! — Preceding unsigned comment added by 98.189.48.210 (talk) 19:58, 13 November 2012 (UTC)[reply]
