Transpkg Reuse lists local downloaded packages that can be reused when downloading new versions.
Listed local packages may share common files with new version and thus making them excluded from redownloading.
TransPkg Reuse is just the same TransPkg but reused all prev versions not just current one.
Note: This feature makes downloading process faster even if it makes transpkgs less reusable.
What is the idea?
-
When the user wants to download a package, they have to declare their current version and the version they want to update to. Also, if there is any information that may help make updates faster, the user should provide that info as well (e.g. List of all locally cached versions of this pkg that can be reused).
-
The Server has to generate a transpkg with differential updates. A package with updates does exclude everything that can be reused locally when user will unpack (extract) that transpkg to get updated version of the pkg. The servers will work as a person that compresses stuff when the user will have tools to extract/restore/unpack it back
-
Low Internet Connection Feature or The Servers Working Harder Feature (depending on what role you play): The servers are spending extra time on the 2nd step to identify renamed files, or even renamed and updated files (or seemingly renamed and updated files), searching all mentioned pkgs for content that can be reused, looking for minimal differences. Excluding publicly known copies like Licenses (that are always the same) that can be preinstalled with an app as the most commonly reused stuff.
-
Unpacking Time or Package Transition Process: The user downloads compressed transpkg and then starts to reuse cached pkgs and reusing all the data that transpkg tell them to reuse. Since the Server had done all the work, the client side just has to follow instructions to get the desired updated pkg.
-
Magic, you spent less time being online by reusing offline stuff.