gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: hemppah
Subject: Re: [Gzz-commits] manuscripts/storm article.rst
Date: Tue, 28 Jan 2003 12:26:26 +0200
User-agent: Internet Messaging Program (IMP) 3.1

Quoting Benja Fallenstein <address@hidden>:

> 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).

Yes, I understood your original point ;).

My point was that by using hashing (and IDs) some locality properties are lost,
which are benefitial in *some* cases. But AFAIK, these locality (which are cited
in the publication) properties are not important for us.


-Hermanni

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]