Let's say that we have "packageA" with "my.exe" that needs to go to your Site Server/Package Server and then to the client machines on the assigned Sites to that Site Server/Package Server.
Then days later, you modify the "packageA" with a newer version of the "my.exe" file
1. When there is a new "my.exe" version for "packageA", does the Site Server/Package Server delete the old file and then download the new file? Or keeps the old file in the cache folder until the new file is downloaded?
2. What happens if the old file is already downloading on a client machine, does it stop the download process and delete what was downloaded on the client machine? Or keep downloading until it is done and then replace the old file with the new one?
3. What happens if the old "my.exe" is in use (like it is open by the user), will it delay in getting the new version downloaded and replaced until we close the file?
At no time do we delete any files, they are simply overwritten. We also never keep a cache of old files. Package files are determined if they are new or correct by size and date of last change, not by a hash.