Re: Re: Communication of CHANGES

On Mon, Nov 26, 2007 at 09:17:56AM -0500, Mark Phippard wrote:
> > > > However, could you spell out the advantage to be gained from this?
> > >
> > > Well, perhaps speeding up "svn status -u"?
> >
> > No. It's important not to change the existing behavior of anything, in
> > particular svn status. It's important that "svn status" and "svn status
> > -u" continue displaying exactly what they've always done.
>
> I think he simply meant the goal is to display the same information
> ... faster.

Yes, that's what I guess Edward is suggesting.

However, if, as you say, the client always wants to know the latest
revision a file was changed in, as opposed to simply finding out whether
a file in the working copy was out of date, then there is no way
around asking the server anyway. So the cache would be pointless.

-- 
Stefan Sperling <stsp@elego.de>                 Software Developer
elego Software Solutions GmbH                            HRB 77719
Gustav-Meyer-Allee 25, Gebaeude 12        Tel:  +49 30 23 45 86 96 
13355 Berlin                              Fax:  +49 30 23 45 86 95
http://www.elego.de                 Geschaeftsfuehrer: Olaf Wagner