Re: Reserved checkouts

Brian Behlendorf <brian@collab.net> writes:
> I would also ask that reserved checkouts not be made impossible to do, for
> the same reasons.

Oh, not to worry -- nothing in the current design makes them
impossible to implement later. It's a matter of the repository
keeping records about who has checked out what, that's all.

To prove that it's not a problem, here's an implementation:

   1. Client A requests a reserved checkout of tree T

   2. Server sets a non-historical property on T noting that client
      has reserved it and sends T to client.

   3. Client B tries to commit to T, the commit fails because the
      repository notices the property.

   4. Client A releases the reservation. Server removes the
      non-historical property.

   5. Client B commits and succeeds.

With a flexible server-side hook interface, such as Subversion will
have, you don't even need much (any?) extra code in Subversion itself
to support this.
Received on Sat Oct 21 14:36:12 2006