[ge-talk] file versioning

[John Drinkwater]

Maybe I should read up on ZFS, but I'll find it easier asking those
that know: what happens if a part of the version set gets corrupted ?
Does ZFS store versions as differences?
If it's stored as diffs, does that mean a section of my revisions are
lost if only one file got corrupted ?
How often does it decide to "keyframe" my changes?
If any of you have noticed how error-prone keyframe based codecs
(mpeg4, etc) can be, you'd be a little worried about partial files.

Loads more thoughts continue to come out... but i'll just ask those above.

John

On 22/01/07, Ronald Vos <egregius at gmail.com> wrote:
> But isn't this how ZFS intrinsically works? By only writing the diffs it can
> maintain loging-like write-by-appending (that makes ZFS performant), with
> the added side-effect of getting versioning for free. At least, that's how I
> believe it to be.
>
>
> On 1/21/07, Paul van Nugteren <pmvannugteren at eml.cc> wrote:
> > Sure, just be informed that binary files like images and such can't or
> > can't be easily diff'ed.
> >
> > On Sat, 20 Jan 2007 21:39:20 -0500, "Ari Haviv" <arielbhaviv at gmail.com >
> > said:
> > > Most software developers are familiar with versioning systems such as
> > > CVS, Subversion or Mercurial. You maintain previous versions, you
> > > fork, you merge. What I'm thinking about and want to bring to the
> > > table is having this concept for any large project including documents
> > > and multimedia files. And it should be easy to use.


-- 
John '[Beta]' Drinkwater
http://johndrinkwater.name/