android - Git for Peer to Peer content distribution network -

Is such a git using GIT?

I would like to distribute some multimedia content to a server I would like to send back a log file with the device usage statistics (I will write through an Android app) .

The server may be anything but I would prefer a Linux box.

I thought that since the only difference between the GIT handle and the files, the only difference will be a good tool for this purpose and I will have a material revision history in the form of bonuses.

I recommend how repository architecture can be organized: should it be a star topology or something different?

The system's remote end does not need any interactivity, in other words, the remote GIT can pull the repository and it can be done automatically and automatically, whatever it may be.

Update: I'm talking about the author of git internals (I'm downloading it now), Scott Chacon I would like to apply the architecture

Update 2: OK, I read the chapter about "the use of non-SCM GIT" and that the author tells Peer about Peer CDN:

You have to get new content [...] XML files, images, animations, text and any of the sound It is also to be consist of combining. You need to build a content delivery framework that can easily and efficiently move all the necessary material on your network to the machines. You need to consistently determine which content each machine has and what is needed and as efficiently as possible in the difference. [...] It has been found that Git is an excellent solution to this problem.

I have not found anything about some parts of that book, so I hope that I am not violating any copyright. In any case, I will remove it if someone complains.

So in the previous job, we have used the guitar exactly like this and the reason was that Our media assets did not change often, so whatever we use does not matter that we have to send the entire file in any way - in this way, issues related to binary, although other content distribution tools were not important.

The main advantage for rsync (and possibly uniting, though I have never used it) is that you can build the content tree in the index and store the trees in Git Instead of having everything on the disk to run Rsync, branch per client. If you have a lot of changes on the material, then it is good to be able to record the unique tree of every material required by each customer - of which you can add thousands of combinations - and a simple pull command only get what the client Update on and update it This is the reason why we choose to do this instead of rsync. If every customer needs a similar set of data, then RCIN might be easy, but the other good thing about Git is that you get a history of content on every customer - when and how it changes for each client Gaya.

We also used it to record log files - since they are usually very similar and text based, they transmit delta excellently and very efficiently - we record our log data and It was very pleased to use it to move back.