It wouldn't be that hard to do from the slide end - it could be via a
separate experimental store for now.
The problem is usually a practical one. For example, let's suppose you run
your binary file through uuencode and diff that - you could store a set of
diffs, but you'd probably find that you wind up storing just about the
entire file anyway because a change is likely to bit-shift and change all
the ascii from then on. It's basically a case of 8-bit to printable
conversion.
Now, if instead of that you dispense with printable diffs (and you could in
the case of slide), you could integrate in something like:
http://filewatcher.org/file_i/33296327/xdelta.html.
Neat little project for someone.
Peter
-----Original Message-----
From: Kelvin Tan [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 19 June 2001 7:07 PM
To: [EMAIL PROTECTED]
Subject: Binary Version Control
Not sure how relevant this is to the Slide-User list, but I'll give it a
shot.
Content management isn't just about managing text. It's also about managing
binary data. Currently we have CVS and Diff to perform version-control (and
storing the differences) for text. Is there a binary equivalent?
If I upload a 10MB binary file and check it out, then check in a 10.1MB
binary file, wouldn't it be neat if the content management system could
store just the difference?
I understand rsync performs something similar, though I'm not too clear
about it.
Comments?
