> > Internally, Subversion uses a binary diff algorithm to express all
> > file differences, regardless of whether a file contains text or binary
> > data. So when you store successive versions of a binary file in a
> > Subversion repository, you *are* getting differential (compressed)
> > storage.
>
> Yes, but the size of the diff is increased tremendously because gzip
> messes it up. Try gzipping one file, make a small change to the file,
> gzip again and compare. This isn't something we can trivially solve
> I think.
>
Just a thought:
- gunzip such compressed xml-files to a temp file, use that for
the subversion client. AFAIK the berkeley db uses compression
itself to store the files in the repository so there wouldn't be any
space wasted 'cause of that.
- when Subversion delivers such files and stores them in the working
copy again fist store it to a temp file and then gzip it again.
This would mean to implement another step between loading/storing
files from/to the working copy.
I don't know how much work that would be but if that's a file format
that's supposed to become very popular then it might be worth the
effort.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 24 19:52:38 2003