Background Updates/Implementation Strategies: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 55: Line 55:


[[User:LawrenceMandel|LawrenceMandel]] Is there a build id/timestamp? Is that a suitable identifier to use? Would this method break if FF moved off of hg?
[[User:LawrenceMandel|LawrenceMandel]] Is there a build id/timestamp? Is that a suitable identifier to use? Would this method break if FF moved off of hg?
(ehsan) There is a build ID, but using that would fail for updating across branches.  I don't really want to use timestamps since they are prone to all sorts of race conditions, and also to the correctness of the clock on our builders/users' machines.  I don't know of any other suitable identifiers.  Moving off from hg would break this unless we come up with a way to get a repository index from the repository.  I would imagine that any RCS that we would use would have to have a similar concept.  Since we only use the revision ID for uniqueness, it's treated as an opaque value so switching away from hg won't affect it.
(ehsan) There is a build ID, but using that would fail for updating across branches.  I don't really want to use timestamps since they are prone to all sorts of race conditions, and also to the correctness of the clock on our builders/users' machines.  I don't know of any other suitable identifiers.  Moving off from hg would break this unless we come up with a way to get a repository index from the repository.  I would imagine that any RCS that we would use would have to have a similar concept.  Since we only use the revision ID for uniqueness, it's treated as an opaque value so switching away from hg won't affect it.


Confirmed users
657

edits

Navigation menu