--- Comment #6 from Gabriel Wicke <> ---
(In reply to comment #5)
> Unfortunately, commit hashes are not time-ordered, and we presupposed that
> clients would move forward.

Our commits table has a timestamp for each commit (IIRC based on the actual
commit timestamp even). This makes it possible to determine what the last known
commit is.

> We could reject incoming requests if they are not
> from either:
> - The latest recorded commit hash, or
> - A completely new commit hash that we didn't know about.
> That would introduce a delay, though…

We can just store the hashes we know about and the latest hash in variables.
Checking those is cheap and should not add any appreciable delay.

You are receiving this mail because:
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to