GWC telling me Phex is.....
 

some GWC says Phex support both Gnutella1 and Gnutella2, is it true? i mean does it support Apprication/x-gnutella2 stream? because it is totally different packet layout and is not compatible, if not supporting the packet, should not tell GWC Phex is aware of Gnutella2, since it will pollute HostCache a lot.

Not sure what Gnutella2 is... must be a fake... :wc:
Phex only uses the standard GWebCache protocol and doesn't claim to support anything else...

Phex doesn't support Gnutella2, since there is no such thing as Gnutella2.

What you're referring to is Mikes Protocol or the Shareaza Protocol, which is in no way a followup on Gnutella, but a completely different network.

Sadly its performance can't be judged nicely, since Shareaza and the other clients who support it all have a quite substandard Gnutella implementation.

But Phex also doesn't support the Shareaza Protocol, since we believe it best to stick to one network to avoid wasting bandwidth.

And even though you might have heard other things, there are quite good reasons, why Gnutella scales quite well.

yeah, fine and saying "X-Feature: g2/1.0", if you do not accept that to be called as Gnutella2, do not even say it as G2 then:D :giggle: :giggle: :giggle: :giggle: :giggle: :giggle: :giggle: :giggle: :giggle:

It seems CyberBob is right on this one.

I don't know why, but it sneaked into our download code:

src/phex/download/DownloadEngine.java:
But I have a clue, why it is in there: Shareaza did simply use the Gnutella download mechanism in the beginning and just added a header: "Are you a shareaza with G2? If not, then to hell with you! If yes, then please go on downloading. I'll be downloading from you in any case."

I don't know, if they still act that way.

Everything that is to be said about this header was already written long time ago in this thread.
http://www.gnutellaforums.com/showth...017#post147317

Since Shareaza always rejected that there are nodes in Gnutella search results, download mash or downloading files, without having the Gnutella network enabled, this header should never be send and should not cause any problems.
And AFAIK Shareaza, while still polluting, ignores this header already anyway...

This has nothing to do with GWebCache though...

Are you still with us, CyberBob?

Could you try to get in contact with the Shareaza devs and ask them, if Shareaza changed its behaviour?

The default behavior of shareaza(with default setting), if it is not connected to the network, then no upload/download with that network. and it is fine to do it on PHEX, since it has been identified quite long time ago, and if Agent name is PHEX and saying G2, force identifying it as Gnutella1 node anyway. but what i am really wondering is not that part. some SKULL based GWC(GWC which support both G1/G2 as separate cache) was saying PHEX is G1/2 node, which means something wrong in GWC interuction, like PHEX might telling that it is G1/2 aware peer. which can cause some problem since Gnutella2(a.k.a. Mike's Protocol) is basically different format(handshake is same). I, very new member of shareaza Developer, do not want any cache pollution.

.

Could you ask the Skull developer, if maybe there's an error on his/her side?

To our knowledge Phex doesn't claim being G2 in any way, and a complete grepping through the sources didn't return any results.

It is as much in our interest as in yours, to not have any gwc pollution, because that would harm both networks.