DonationCoder.com Software > Find And Run Robot

Updates: Patches?

<< < (2/2)

herojoker:
Aah, you just mentioned the obvious third possibility:
Complete files are downloaded if they are new, but only new ones (I had only direct (binary) patching of the files in my mind before).
This process can be simplified if the patches I mentioned before are replaced by simple text files containing the files changed or added.
For example:

patch_2.22.01-2.23.01.txt:
* changed.xyz
* anotherchange.xyz
+ file1.new
+ file2.new
- removed.foo

These files could then be downloaded from a certain directory on the server.

Of course there are again many ways to build the whole system:
1. Patch files only from one version to the next one
2. Patch files created on demand from arbitrary versions to others (only one time for each patch)
...

If the first way is used the updater should first collect every patch file from the current version up to the desired target version (cumulative; skipping doubles) and then do the work. This way a patching cascade is avoided and also the server load is not so high. Only a bit space is needed for all the different versions. If mouser installs a versioning system even this is not a problem anymore (because internally only diffs are stored).

Perhaps a mix of the download-whole-updated-files approach and the download-binary-patches approach may be useful, because I guess it is the FindAndRunRobot.exe which is updated most oftenly and this file is quite big (currently 3.81MB), a binary patch will be probably much smaller.

Navigation

[0] Message Index

[*] Previous page