Re: Tracing and tracking commits in the new system.

On Tue, Mar 19, 2002 at 02:27:06PM -0600, Karl Fogel wrote:
> cmpilato@collab.net writes:
> > Ooooh...I did so forget about this. Hm...this would mean the RA layer
> > wouldn't need a bump function at all...nice...
>
> Yah. I guess it's always been the case that it doesn't need a bump
> function, but we'd been doing it from the RA layer because it had to
> set RA-specific wcprops anyway (I think that was the reason...).

RA needed a bump function because ra_dav didn't need to track the items in
memory(*). At some point, however, we added the tracking to ra_dav. Thus,
all RA implementations are tracking; thus, we can now move the bump handling
outside of RA.

Of course, this *does* mean we have to accept the reality of buffering all
of that data in memory, in the client.

Cheers,
-g

(*) ra_dav had the server tell it what was actually changed in the commit,
    which meant that the client didn't have to record it. however, the
    server included bubbled-up directories in its change list. if we omitted
    the bubble-up changes from the server's response, then we could remove
    the tracking in ra_dav. this latter algorithm is my favored approach.

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org