Frequently, I'll send out a search for a file, get a list of results, and then search for the same file again a few moments later. Obviously, since a users connection gets better (supposedly) the longer a user stays on, it is a good idea to search for a file over and over again, until the best results are found.
I've been trying to figure out a way to click on the name tab of the search and have it send out the search again, but I haven't seen this option anywhere. Instead, I have to re-type the search over and over again until I get what I want. It gets a little ridiculous after you've re-typed the same entry 20 times. Could somebody please add a "re-search" button, or a control-click menu selection (right-click for PC users) for these searches.

Thanks

This would clog the network , they actually considered this before .
Too make it feasable there would have to be a button to re-search every X mins and auto-download the best result .

The minimum time for that re-search would have to be atleast 10 mins .
Else you will overload the network with query's and results .

And the "best result" should be able to be spicified by the user .
For example the best result is :
A) biggest file
B) fastest connection
C) best matching to initial search keywords
D) ...
And the user could shoose from that .

This basicly makes it posible to start a search and come back 3 days later and be sure you have the desired file .

The re-searching was added for LimeWire 1.9 (and should be in 2 as well).

<http://www.gnutellaforums.com/showth...6440#post20163>

Yes I now , but i mean automatic re-searching at a regular intervals and then auto-downloading the best result .

Thus making LW self-effiecient and not requiring user-input .
Like it is now you have to push the re-search button everytime .

That's scheduled for release in 2.1. The danger is that it can flood the network with queries if programmed abusively.

Yes , I realize that if used wrongly this can clog the network , but can also be usefull for those "rare" and hard to find files .

Maybe we can have a routine build in wich disables auto re-searching if the initial search turned up more then say 50 results ?