"C. Michael Pilato" <email@example.com> wrote on 08/28/2006
> We do client->server deltas using our pristine text-bases for a
> -- to reduce the cost of network transfer. We know that on some
> networks, this matters (trust me -- many folks I know still use 56k
> dialup lines), and on some, it really doesn't. But Subversion
> know which networks are which. Only humans do. And the type of
> in use isn't a property of the file in question, or even of the
> copy in question (hello, laptops moving from place to place) --
> condition as ever-changing as the weather in Chicago that has to be
> evaluated anew each time a commit occurs.
I guess I was thinking that we were only trying to solve the case
have a largeish binary file and we know, because the user told us, that
the file is not going to deltify well. This seems to be a very common
problem and the speedup would come from skipping that step and just
sending the entire file. This problem has nothing to do with network
speed because the real problem is that we are spending a lot of time
trying to deltify the file and the delta being produced is not
significantly smaller than the original.
It sounds like you are trying to solve more problems than just this one,
which is fine. I just did not realize that people were trying to do
i would agree with this poster, a mechanism to enable a user to turn off
"deltification" would go a long way to solving this issue.
i know a head of time which of my files are large binary ones that
well, and its no problem at all to add some kind of svn property to
is this something that the developers on this list think could make
the 1.5 release?
Received on Fri Sep 1 10:29:10 2006