Sorry, but it isnt. Something has to be done about hashing in DC++.
I am sure no one that store their shit localy even bothers, but for those of us who keep our shit on fileservers hash indexing seriously damages dc++ stability.
Hash Indexing by itself is a good idea. However, given all immensly poor fileserver protocols we have to use hash is not always that pleasant. Any idea how long tiem ita takes to hash 0.1TB from samba? Well, even with a samba server running at top speed it takes around eight (8!!!) hours. Eight friggin hours! Given samba is slower like crap it usually takes around 10-12 hours.
This is really an issue for samba to fix, but they seem very content with samba performing at this horrid speed so I dont expect anything to happend there.
Unless you are aware of it, I am pretty sure you are, but every time Windows screws upp and fails to connect a network unit DC++ will start with 20-40% of your actual share and start rehashing (removing in this case) your whole hash index. And I doubt any one is surprised by windows crapping out on its regular bootup tasks like for example connecting network units.
Id REALLY APPRECIATE it if the hashfiles was locked down after hashing because spending 10 hours rehashing your files every now and then is just painful. Then you would manually update them whenever there was a need for it - that way you would put the controls back into the hands of the users (thats where they belong anyway) and these unfortunate mishap wouldnt need to happend ever again.
(Yes, DC++ just started rehashing my gigazilion of data because my fileserver was disconencted by XP - I am not counting on being able to use my computer for antyhing else useful before next weekend or something like that
) And no, I wont stick to Kazaa or bittorent. This is a flaw that needs attention, thats why I am writing this post... you already know well enough dc++ kick ass in many other areas.
)