Quote:
|
Nope.. Reduce traffic actuially.. Since you would only do a search for hash when you allready know what file you are downloading. Otherwise the clients need to search using normal search methods, in order to find a hash.. No real increase in traffic..
|
Of course there would be an increase. You said "There would simply be two queries.. ". One for the initial search (plain text results), the second for the hash.
But as each client responds to a Query, they already include the hash as defined with HUGE. So you already have all the locations the search has to offer. If you send out a new search with just a hash from those result sets, the same ones that sent them in the first search will be sending a result back to you. That's double work for the same results you'll get.
The only exception is when you search using the hash on a new connection. But that's not much of a use. Once you connect to a client to download, you can get alternate locations based on the hash. So you automatically expand your horizon for that particular file. You could even do that *without* any further searches or even download.
Now I'm wondering though: You are familiar with HUGE, right?