Am Donnerstag, 5. Februar 2004 17:29 schrob Jeroen Asselman: > I assume you are looking at the file ~/.gtk-gnutella/dmesh ? > And you expect gtk-gnutella to also do the same for uploads? Aren't you > afraid that if gtk-gnutella would do this, for every file you have > uploaded (and share) it would consume diskspace. Perhaps this isn't that > much of a problem, but how do you expect gtk-gnutella to verify these > alternate upload locations are still valid when they are being stored > across sessions?
I don't see why uploaded and downloaded files should be treated differently, however. Your first point was about disk usage. Yes, storing alternate locations consumes a little disk space. But storing altlocs for an uploaded file doesn't take more disk space than the corresponding information for a downloaded file. I don't see a difference here. Your second point was about validity of the altlocs. Here again, I cannot see a difference between uploaded and downloaded files. Of course, an uploaded file location is not likely to be valid over a long time. But neither are the altlocs of a downloaded file. That's why older entries of the mesh are to be deleted. I can't see the difference between uploaded an downloaded files in this point. Hauke Hachmann ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Gtk-gnutella-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
