Slashdot Mirror

← Back to Stories (view on slashdot.org)

Gnutella2 Specs - Part 1

Posted by ryuzaki0 on from the double-your-pleasure dept.

Mr Fodder writes "The first part of the Gnutella2 specs are finally up." Our previous Gnutella2 story has a little more information.

3 of 174 comments (clear)

  1. Shareaza's gnutella? by Superfarstucker · · Score: 5, Informative

    Shareaza is the only gnutella client that even uses this '2.0' protocol so im more inclined to say that its not really a new gnutella protocol but more or less an extension of the current gnutella client (apparently they didnt like the rate @ which gnutella was progressing)..

  2. Re:I may be wrong by Anenga · · Score: 5, Informative

    Well, here's the story.

    Micheal Stokes (Shareaza developer>) thought that the GDF (Gnutella Developers Forum) was a too slow at fixing Gnutella's problems (unscalable, too much unused bandwidth, unorgnaized for future additions) so he went ahead himself (by himself) and wrote Gnutella2. He has done this before, when he wrote the spec for "Remote Queueing" (kind of like IRC). He wrote his spec first, developed it in his client, released it then proposed the idea to the GDF. The GDF likes it and now Limewire, Bearshare and Gnucleus all support it.

    The GDF is pissed that Mike went ahead and "updated Gnutella" without asking them first. Granted, they have a right to. The GDF is meant to be a consensus, a forum for all developers. And a "assumed" condition of that is to let the other developers know *ahead of time* before going ahead and doing something this massive. And the entire idea that he called it "Gnutella2" (using the Gnutella brand) and advertised it as the "next revolution in P2P" (which it actually, IMO, is) pisses them off even more.

    However, if you notice, it seems only the developers with corperate ties are pissed. Other clients such as GTK (Linux), Gnucleus, etc. all seem interested in the protocol, I believe GTK already said they'd implament it. Limewire and BearShare still seem upset. (It's like owning a oil company, then someone comes out with electricty - sucks).

    Anyways, Mike likes the Gnutella ideals - that it is open and free. So he called it "Gnutella2". Partly to "refresh" Gnutella and revive Gnutella's bad image it has with the general user (which it has achieved IMO) and to show users it's the "second generation" of Gnutella.

    The Protocol is being released now. This is part one, the next one will go over the new packet encapsulation and what not.

  3. the real gnutella by asv108 · · Score: 5, Informative
    As mentioned in previous posts, the specification posted has nothing to do with Gnutella, Sharazea is just stealing a widely recognized name, this specification has nothing to do with Gnutella. If your interested in real gnutella development go to the Gnutella Developers Forum. There are quite a few open source clients available, the most popular being Limewire and Gnucleus.

    I've been playing around with the limewire source for ahwile, it is well documented and there is no spyware in the open source version. I love how people complain about Limewire and spyware, when it is open source. Anyone can take the gpled limewire source and package it without spyware without having to reverse engineer it like closed source KaZaa.