Re: [Gzz-commits] manuscripts/storm article.rst

[Benja Fallenstein]

address@hidden wrote:
> Quoting Benja Fallenstein <address@hidden>:
>
>
> > CVSROOT:        /cvsroot/gzz
> > Module name:    manuscripts
> > Changes by:     Benja Fallenstein <address@hidden>        03/01/25 13:34:09
> >
> > Modified files:
> > 	storm          : article.rst 
> >
> > Log message:
> >         start section on block storage
>
>
> > +When used in a network environment, Storm ids do not provide
> > +a hint as to where in the network the matching block can be found.
> > +However, current peer-to-peer systems could be used to
> > +find blocks in a distributed fashion; for example, Freenet [ref]
> > +and some Gnutella clients [ref] also use SHA-1-based identifiers.
>
>
> -For 'dot not provide a hint', something about data locality *might* be good,
> e.g. http://www.cs.rice.edu/Conferences/IPTPS02/169.pdf: 'This is not *always* a
> good thing, but in Storm, this is a good, because...'

Maybe, but this is not what I mean: I mean that you do not know which 
server holds a permanent copy (i.e., you cannot use it like a URL which 
provides a direct path to the server that'll give you the data).

> -For Gnutella-like clients, there are magnet-uris, which are used in Shareaza
> (based on Gnutella2) and in few other clients. Additionally, edk2k and Overnet
> also uses hash-links for data retrieval.

Yes, good reference!

> Btw, when I make comments on commits, should we first discuss these things on
> the list, or, should I directly write these things into the text ?-)

Either is fine with me. :) Probably when you can write text that could 
go into the article, put it there, and when you have comments but aren't 
able to write article text yet, send them to the list...

-b.