[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: update processing

From: Ben Collins-Sussman <sussman_at_newton.collab.net>
Date: 2000-12-14 16:38:48 CET

Greg Stein <gstein@lyra.org> writes:

> b) We send one big mother request about the client state.
>
> This corresponds to the "close_edit" strategy that Ben mentions in
> svn_ra.h.

Indeed, this is the only real thing we can do, and it's a big "hunka"
server work, as you said. Specifically, it's a big hunka filesystem
work.

The client sends a tree-delta devoid of text-deltas; this tree-delta
gives a root revision #, and then "replaces" any file or dir which is
at a *different* revision #.

The filesystem then builds a mini-node-tree, floating in space, which
is a model of the working copy. The filesystem then compares this
tree to the "head" tree, and sends back a custom tree-delta.

Does everyone agree on this model now?
Received on Sat Oct 21 14:36:17 2006

This is an archived mail posted to the Subversion Dev mailing list.