Auto-requeries!

[Dulcina Jinx]

Yes, it is public alpha. But the alpha has a ten day expiration date, and it will refuse to work after that time. And there is also very small number of people using that alpha. We really can't say that it is hurting the network if there is only a few users using that client.



And back to the original issue. If you have read that thread to the end, you would notice that there is a solution for it already, even if the new alpha haven't been released yet. The problem was that the requery interval was set to zero. And because there was no other users complaining about that, the default value was correct with most users (for some reason I had the wrong value). So, actually I was the only user flooding the network with BearShare.

[Plinko]

It seems that auto-requeries are not so easy to handle as Vinnie thought:

http://www.bearshare.net/forum/showthread.php?threadid=12772

But he was able to badmouth Phex and Xolox, because they are unhealthy for the Gnutella net, he wanted to block them!

Should we now block bearshare too?

Morgwen

[thunderdragon191]

Well, that's one of the reasons for Bearshare 3.0 is still alpha. What do you expect? At least it was not intended that way.

[jlb299]

No taliban troll, the funny part is that Vinnie was badmouthing and blocking others for something he does even worse now. Well, now that he understand the importance of requeries as a key technology (and he fix his problems), we might see him cooperate with his hated Xolox in a few years.

[Razamvmt/mya]

Everybody who change this value is flooding the Gnet, such an option should not be changegable...

Only some users use this alpha? Everybody is able to download it so how do you know how many people are using this alpha?

You should test the alpha in private... like other do too!

Morgwen

P.S.:

The solution was posted after I created this thread here, check the dates!

[legitimate junkiee]

I'm pretty sure that it will not be changeable in the release version. If it is fixed in next alpha, after the present alpha is expired there are no user flooding the network.



Run any client what is capaple to show what make of host it is connected to. It will be quite a hard work to find a BearShare 3.0.0.aXX user. Or search something, it won't be that easier to find 3.0.0.axx users in that way either.



Releasing the alpha in public gives you a lot of comments from users. Bugs are found much faster than in closed and limited testing enviroments. And because all alphas cam be used only a limited amoun of time, the possible harmful alpha version will not continue harming the network too long.

And it gives a good feeling to the most active users, they can take part to the developing process.



That was my mistake. I'm sorry about that.

[Tom]

Yes A "PUBLIC" alpha... so if he test this alpha in the public he "IS HURTING" the Gnet.

He shouldn

[sugarcraver]

Well, Morgwen, that's your opinion, - and it's also your problem.

[Mary W]

someone said: "You should test the alpha in private... like other do too!"

If the alpha were not public then how would this bug have been discovered? There is a difference between INTENTIONALLY requerying at short intervals and a BUG. Luckily, the bug was caught before 3.0 went final, so it does not cause harm to the gnutella network at a large scale. XoloX and friends didn't care about the effects their aggressive re-querying behaviour would have (Don't even try to say that XoloX wouldn't/hasn't harm the the gnutella network. You just said that BearShare would harm the network with agressive requerying). XoloX dont even have public betas.

[Rafe]

wrong, look into the xolox forum