Hi, I'll try to explain myself better.
Op za 07-02-2004, om 19:59 schreef Haxe: > 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. Well, say you download 100 files, assume every file has 10 alternate locations. This means you only have to save 1000 alternate locations. Lets say every alternate location take 25 bytes. So, this would take 25000 bytes to store for downloads. Not that much. No, say you (or people) share 10.000 files, this would mean 100.000 alternate locations. Which means 2500.000 bytes off storage. OK, we aren't talking about megabytes here. But just as an indication. However, lets continue to the second argument. > > 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. When you download a file, and try the alternate locations, you automatically test the validation of an alternate location. If an alternate location gives you a 404 error on download the alternate location is not valid anymore. End of story. If the alternate location is busy or you can start downloading, the alternate location is valid. So, on download verification of an alternate location happens automatically. It is just part of the download process. With uploading a file this is not possible though. Unless gtkg would start sending an download request to every alternate location for all files shared. So in the example above we would send 100.000 of download request for a file we allready have. Waste of bandwith. Or do you dissagree on this point? (Issueing a download request is more then sending/receiving a few bytes) That is why gtkg only keeps the alternate locations for uploaded files for a relative short amount of time in memory while it is running. However, I do admit it would be nice to have some way to track the files one has upload to provide better results. -- Jeroen Asselman <[EMAIL PROTECTED]>
signature.asc
Description: Dit berichtdeel is digitaal ondertekend
