Don't search immediately with search for alternates.
Moderator: Moderators
-
- Posts: 73
- Joined: 2003-01-06 09:32
Don't search immediately with search for alternates.
I'd like to see a slight change in the behaviour of the manually started search for alternates.
As this functionality is now, DC++ automatically sends out a search with a search string which is basically the whole filename. However, most similar files won't be found this way because there are always several filenames in use for the same file. This amounts to another search in which i've altered the searchstring to get beter results.
What i'd like to see is DC++ opening the search window as it does now, but not sending out the search. This way i don't have to count to 5 to avoid search-spamming, and some bandwith/cpu-time on the hubs and other users is saved.
I'd think this would be a slightly more elegant way for the search, but maybe i'm the only one who alters those searchstrings.....
As this functionality is now, DC++ automatically sends out a search with a search string which is basically the whole filename. However, most similar files won't be found this way because there are always several filenames in use for the same file. This amounts to another search in which i've altered the searchstring to get beter results.
What i'd like to see is DC++ opening the search window as it does now, but not sending out the search. This way i don't have to count to 5 to avoid search-spamming, and some bandwith/cpu-time on the hubs and other users is saved.
I'd think this would be a slightly more elegant way for the search, but maybe i'm the only one who alters those searchstrings.....
Great suggestion!
i want this too!!
i want this too!!
http://whyrar.omfg.se - Guide to RAR and DC behaviour!
http://bodstrom.omfg.se - Bodströmsamhället, Länksamling om hoten mot vår personliga integritet
http://bodstrom.omfg.se - Bodströmsamhället, Länksamling om hoten mot vår personliga integritet
-
- DC++ Contributor
- Posts: 3212
- Joined: 2003-01-07 21:46
- Location: .pa.us
-
- DC++ Contributor
- Posts: 3212
- Joined: 2003-01-07 21:46
- Location: .pa.us
I'm sure the $Search string is pretty unique in autosearches - it doesn't do whitespace collapsing, and both the type and the extension should be in it. It's probably not easy to do with a script, especially not if you can't easily capture the first search by a user - or the first dozen. But scripting the behavior seems possible...?[Rai] wrote:It would be handy if search for alternatives was shown in the DC++ tag as many hub owners may not want users to have this feature activated.
How many other features could possibly go into the tag that hub owners would like to discourage? It could, in theory, get huge and unreadable.
I agree the change is needed, as I need to change the search string as well every so often and then search again. It could cut the bandwidth needed for searching quite a bit.
To get up the window with the original search string and then having to press search is a lot better. Remember that searching takes up quite a bit of bandwidth on the client side as well, not only the hubs would benefit.
To get up the window with the original search string and then having to press search is a lot better. Remember that searching takes up quite a bit of bandwidth on the client side as well, not only the hubs would benefit.
naah, this matter is easily handled with a hubscript.. just don't allow searches more than every X minutes... no need to make a fakable tag out of it![Rai] wrote:It would be handy if search for alternatives was shown in the DC++ tag as many hub owners may not want users to have this feature activated.
agree fully, this is a change that will benefit everyone, but maybe there could be a setting for the search behaviour, some ppl might like it the way it is.. and might also get confused and think DC++ is not working correctly if it suddenly changed behaviour!distiller wrote:I agree the change is needed, as I need to change the search string as well every so often and then search again. It could cut the bandwidth needed for searching quite a bit.
Regarding the matter of these 10/5 seconds search timeouts. I undestand the hubowners need it, search strings represent a large amount of the total bandwidth used. I would like a feature that make this thingy less irritating clientside, an own search timeout.. it would work like this.
* I set my client search timeout to 10 seconds.
* I do a search which immediatly triggers my search timer, ciunting down from 10.
* After 6 seconds i do another search, which isn't sent until my timer is on 0.
This will have this effect:
1. The hub don't have to recieve and handle abusive searches.
2. The hub don't have to answer all the abusive searches with "Ignored, 10 second timeout".
3. I don't have to wait for my search results to come up, not yet knowing it have been ignored.
4. I don't have to research again only to find that I once again was to fast and my second search have been ignored also!!
so.. watcha think?
http://whyrar.omfg.se - Guide to RAR and DC behaviour!
http://bodstrom.omfg.se - Bodströmsamhället, Länksamling om hoten mot vår personliga integritet
http://bodstrom.omfg.se - Bodströmsamhället, Länksamling om hoten mot vår personliga integritet