Hi, On Thu, Apr 25, 2013 at 3:08 PM, Marcel Reutegger <[email protected]> wrote: >> Note that the SegmentMK is designed to avoid this problem; it can >> guarantee that the commit hooks get run against the latest state of >> the repository and thus can't possibly conflict. > > it does it with a retry logic, right?
Yes. If there were other concurrent changes, the current change set is rebased and commit hooks re-applied before the retry. > the same could be implemented in the KernelNodeStore... We'd need to revise the MicroKernel contract for that, essentially to require that a commit be rejected if it isn't based on the latest revision. Without separate journals like in the SegmentMK, that would introduce a major scalability bottleneck. BR, Jukka Zitting
