Is it too difficult to integrate Subversion into a simple file archive application?

Question

When we are going to start planning an application that will process media files (mp3, flv, pdf, images), I think about how to handle file storage. Files will change, and versions should be tracked to the extent, so you need to integrate SVN into the application.

Now I wonder is this too much? I'm sure that we will use only part of the power of SVN, so maybe just pointing to the file system using the database would be just as good.

On the other hand, these custom archive solutions always become very ad hoc, and this time I would like to get a reliable solution. Too much trouble? What do you think?

Answer 1

The problem that I can think of in SVN is that it will grow steadily with large binary environments (very little, if any, diff), and it is very difficult to clear the history of SVN. As long as you know what you are doing, everything should be fine ...

Answer 2

Subversion is really quite simple, especially on a Windows platform with TortoiseSVN. Using it to archive media files in a simple scenario is probably not a bad idea at first glance.

If you encounter a problem, all of these file types are binary and therefore cannot be distinguished. Because of this, your repository will grow quite large, and you will not be able to easily compare changes between the two versions.

, , , , !

Answer 3

, .

mp3, flv pdf . Subversion , . , subversion , . , .

? , , . . , . , , , .

Answer 4

, , , - .