Re: Implementing a Gnutella-structured network only with basic HTTP possible?Date: Wed, 24 Feb 2010 09:08:15 +0000 (UTC)Date: Fri, 26 Feb 2010 12:55:15 +0000 (UTC)Date: Fri, 26 Feb 2010 20:45:27 +0000 (UTC)

[email protected] Fri, 26 Feb 2010 21:45:28 +0100
Newsgroups gmane.network.gnutella.devel
Organization Home, Grenoble, France
Message-ID <[email protected]>
Quoting Max <[email protected]> from ml.gnutella.dev-forum:
:offload offers even more. you can store a file, go offline, and users still
:can download the file from the network.. DISPERSE is the keyword.
:storing the blocks in the dht, and then going offline, then publishing the
:OFF-hashlink and you still can load from the DHT.. all blocks-.

You keep speaking about "offload", but I've been unable to connect the bits
of information you're giving because I lack the Grand Picture allowing me
to fit all the pieces of the puzzle.

Could you refer us to an academic paper describing the architecture and
the purpose of this system?

From what I've read so far, it looks like "offload" is not the way to go
for Gnutella 3.0.  Its philosophy seems completely alien to the Gnutella
we know.

Just because "offload" has a DHT does not make it a suitable replacement.
For instance: Linux has a process table, Windows also has a process table.
That does not make Windows a suitable replacement for Linux.

Raphael