|
| |||||||
| Register | FAQ | Members List | Calendar | Arcade | Search | Today's Posts | Mark Forums Read |
| General Gnutella Development Discussion For general discussion about Gnutella development. |
|
Welcome to Gnutella Forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. Once registered but before posting, members need to read the Forum Rules (click here) and LimeWire/FrostWire users should include System details - help us to help you (click on blue link) in their posts if their problem relates to using the program. Thank you |
 |
| | LinkBack | Thread Tools | Display Modes |
December 27th, 2007
| |||
| |||
 Gnutella response codes? Is there any reference to what each client's response codes mean what? Bearshare sends the useful 'GNUTELLA/0.6 503 Full' one but I noticed Limewire sending 'GNUTELLA/0.6 593 Hi' which means nothing to me. Also any others you know about would be useful. I'm writing a intelligent GWebCache and I'm looking at more ways to find Ultrapeers and make clients connect faster. One main thing I'm thinking about is sending a crawler request to known ultrapeers. This has two benefits: It allows me to see how full it is and it allows me to find more ultrapeers. There is no point sending users to a full/dead ultrapeer. Feedback and suggestions are welcome. Having a list of response codes would help a lot.  |
|
| Thread Tools | |
| Display Modes | |
| |
Linear Mode
