DeRose: Designing pro creative apps (Part 1-3)

Posted Jul 12, 2011 2:34 UTC (Tue) by cmccabe (guest, #60281)
In reply to: DeRose: Designing pro creative apps (Part 1-3) by cmccabe
Parent article: DeRose: Designing pro creative apps (Part 1-3)

Another thing to consider is just using git. Git is a content tracker, not just a source code tracker.

In order to use git effectively, you will need to segment your media files into bite-size chunks (30 seconds each, maybe?), but that is something that you probably needed to do anyway. You also need some kind of file saying what order the chunks go in.

You will obviously need to provide your own diff function between chunks, but again-- that is something you needed to do anyway. In a distributed system, conflicting versions *will* happen, and people *will* want to resolve the situation (aka merge.)

Git has a very, very efficient, very well-tested codebase. It doesn't require users to run any server besides sshd. It is truly distributed. Basically, you get what is effectively snapshots and revision control for free.

Please remember that usually, git doesn't do a SHA-1 on any objects. Usually, all it has to do is check the timestamps (mtime) of the files in the git repository.

So all in all, I'd use git.