You make it sound like the file formats have been changed without proper reasons. No, the hash database format wasn't changed because of this issue (I just wanted to report my findings here while making the rewrite). Dealing with a hash index XML file that could be several gigabytes in size and being regularly rewritten on disk (or being read into memory) just became too problematic. The same applied to having the whole download queue being stored into a single file vs. splitting the data into several XML files that allows only the changed ones to be rewritten on disk.
I've also written several posts about those changes: https://www.airdcpp.net/forum/viewtopic.php?f=4&t=4007 https://www.airdcpp.net/forum/viewtopic.php?f=4&t=1856 As written in many introductions, AirDC++ is designed to work smoothly even if the user is sharing hundreds of terabytes of data or more than 10 million files. If you don't see any difference compared to DC++ and you rather prefer compatibility with old file formats, it may not be the right client for your use case. -- You received this bug notification because you are a member of Dcplusplus-team, which is subscribed to DC++. https://bugs.launchpad.net/bugs/919424 Title: /rebuild does not update HashData Status in ApexDC++: New Status in DC++: Confirmed Bug description: BCDC 0.790a. Windows 7 SP1 x64. Summary: If you add a new share, hash the files, and then remove it, issue a /rebuild and then re-add the same share again, DC++ will not rehash the files. Furthermore, a /rebuild between adding/removing shares does not change the size of hashdata.dat or hasindex.xml. Repro: * add a new share. accept the default name. DC++ hashes the files. * open your filelist to validate share is present. * check the size of hashdata and hashindex. * remove the share you just added. * issue a /refresh and /rebuild. * note the size of hashdata and hashindex has NOT changed. * add the same share again, accepting the default name. DC++ does NOT hash the files. * issue a /refresh. DC++ does not re-index the files from that share. To manage notifications about this bug go to: https://bugs.launchpad.net/apexdc/+bug/919424/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~linuxdcpp-team Post to : linuxdcpp-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~linuxdcpp-team More help : https://help.launchpad.net/ListHelp
