Hashing of files
March 14, 2007 1 Comment
Something that every so often arises on the (now absent) forum is why DC++ re-hashes some files. People with network drives are among the majority of these users.
There are two reasons why DC++ would (re-)hash a file.
(1) The path to the file has changed. (The file name is included here.)
(2) The file content has changed.
People don’t realize why (1) is important. They think that DC++ could just look at the file name and see “that it’s the same file”. However, this would obviously not work well if you have multiple files named the same (“example.png”) sprinkled through your share.
(2) is obvious if you’re indeed changing the content of a file intentionally. However, there’s some software that “automatically” do this for you. You might experience this the most with MP3 files and documents. Certain media players like to change the ID3 tag of MP3s, and various document editors like to set their own foot print on the files.
People with network shares may see these things regularly. Detaching and re-attaching the network drive may cause them to update the files’ timestamp and may cause DC++ to re-hash the files . Sometimes, the path may also change, causing (1) to happen.