Shareaza

Several years ago it used to be possible to keep shareaza searching for 'rare' files forever
(after clicking search more than 3 times i believe, don't remember very well)

Nowadays Shareaza will always stop searching until you click search again.
I find this a problem big enough to post...

In the past i accomplished to find some very rare files after having Shareaza search for them for about a week or so..

I can't use that old version anymore as i had to update it because more and more edonkey's were kicking off my old client

It could be done without putting to much stain on the network by having some kind of large time interval between successive searches.

I am not interested in answers like:
-Why would you need it/it isn't necessarry etc..

I was wonder that there may be a simple registry tweak for enabling this 'overnight' searching behavior...

If not the only thing i can think of is downloading the sourcecode &try to enabling it there yet
i am no very good programmer so any hints would be greatly appreciated .

I'm directing my question especially to the dev's, as to why it no longer behaves this way...

Again i am not interested in opinions, as when i've set my mind to something i usually persist stuburningly...

I hope anyone can provide me with some usefull information and directives on this, thanx...

&yes, sorry for me english, It is not my native language

You can not do this anymore because too many people left search windows open without closing them, putting an enormous strain on the network.

Set the following settings to maximums for less restrictions: Gnutella.MaxResults, Gnutella.MaxHits, Gnutella2.QueryLimit.

I don't know wheter you're a dev or not...

but what i understand from your answer is that it may not be easy to do this...

If Shareaza is indeed querying independent searches for each search window,
This would be a serious problem as you say.
Then it may be something that should be thought over...
As i don't see any situation where this kind of behavior would be desireable.

Not only for the network, but also in the clients perspective,
as this behavior may hog the clients network connectivity &ability to have a good browser experience while running Shareaza.

If it turns out that Shareaza works as you imply, timing intervals would have to be chosen very high &it will not be able to overcome this issue, only reduce it's negative effects.

If however Shareaza's search function can only be activated in a chronological order by every search window this would not be a problem.
I hope Shareaza works like this but after using it several years i believe you are right about it searching simultaneously.

I probably don't have the skills and-or the will to make huge changes to a program for which the sourcecode is likely to change dramatically in the near future (with each version).

Considering my skills i will make little changes at most.
But i think of this as something i would have to do only as a last resort.

I could write an .AU3 to click search for me but i don't consider that as a solution.
It would then be better to try to change the sourcecode itself or atleast convince the dev's to at least look into this.

I am not convinced that it technically would not be possible to do this without putting extra strain on the client or the network.

If there is a dev that could help me on this or simpathizes/understands why i believe this should be seen as a problem, any help is greatly appreciated.

Help me to convince the dev's to include this into Shareaza !

One last thing,

For files that have many hits searching should not endlessly continiue as this would make no sense...

Your solution to increase maximum hits/results doen't makes any sense as rare files aren't getting any no ? ? ?

only for rare files that don't get any hits, it would be nice that the search would be repeated every x hours or so.

wouldn't that be nice

The thing is G2 has an iterative walk searching mechanism. Meaning the search continues until the entire network is searched (assuming that we have less than 2400 hubs in total). Now this process results in more hits, but at the expense of a large Network crawling. If a search was to run indefinitely two things can potentially occur, one being that you won't find anything because searching the entire network the first round won't improve things much after the n'th time. Second is that the amount of queries created can actually reverse flood back to you (depending on the re-query rate), feeling like your undergoing a DDOS isn't a good thing.

Lastly it undermines the whole essence of searching. Searching is about instant gratification, not a waiting game. G2 is designed as to yield the maximum results. If it ain't found now just search another time of day to improve your luck, in that case your chances of a search result are the same as leaving it on indefinitely.