Quote:
Originally posted by sberlin
verify as it's downloaded, but it's not possible to do that right now. It _will_ be done that way at some point, though. |
I'm not sure about what you mean here.
LW isn't checking downloads against the tiger tree before the final hashing? (well it looks that way as of now) Even with LW verifying a tiger tree chunk that is corrupted while downloaded, you'll have to quarantine hostile clients to finish the download. The yesterdays gnucleus hosts was only 1 of 75 sources, but it always had open uploads slots with great speed -- seems to be intentional to me---. LW gotta protect downloads from those hostiles.
An optimisation would be LW asking sub tiger trees for a often corrupted chunk and disable swarming for those small chunks so LW indentifies the corrupted host. But LW would have to ask the sub tiger trees to a trusty host: that seems difficult, except if you are a Bearshare (read- non hijackable because close source).
Ciao
Edit: concerning memory leaks in uploads: I see magnetmix has america's army ready to download. Suggestion, set a LW with AA shared and monitor memory consomption after idle time and concurrent uploads. I do not have a console in LW to help you debug!