gzz-commits
[Top][All Lists]
Advanced

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

[Gzz-commits] manuscripts/storm short-paper.rst


From: Tuomas J. Lukka
Subject: [Gzz-commits] manuscripts/storm short-paper.rst
Date: Fri, 30 May 2003 08:09:03 -0400

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Tuomas J. Lukka <address@hidden>        03/05/30 08:09:03

Modified files:
        storm          : short-paper.rst 

Log message:
        thanksjvkagain

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/storm/short-paper.rst.diff?tr1=1.19&tr2=1.20&r1=text&r2=text

Patches:
Index: manuscripts/storm/short-paper.rst
diff -u manuscripts/storm/short-paper.rst:1.19 
manuscripts/storm/short-paper.rst:1.20
--- manuscripts/storm/short-paper.rst:1.19      Fri May 30 07:51:03 2003
+++ manuscripts/storm/short-paper.rst   Fri May 30 08:09:03 2003
@@ -85,8 +85,8 @@
 .. using location-independent identifiers for
    non-breaking links:
 
-If desktop documents could be refered to independently
-of their location, it would be feasible to make
+If desktop documents could be referred to independently
+of their location, it would be possible to make
 non-breaking links to them: When a document is published
 on the Web, it would have the same URI as on the
 author's desktop; when a link to a document is emailed,
@@ -132,8 +132,9 @@
 rendered this assumption obsolete. Distributed hashtables (DHTs)
 
[malkhi02viceroy-andalso-maymounkov02kademlia-andalso-ratnasamy01can-andalso-stoica01chord-andalso-zhao01tapestry]_
 
 allow location-independent identifiers
-to be resolved on a global scale. In fact, authors argue in 
-[balakrishnan03semanticfree]_ that DHTs are suitable for the next generation 
+to be resolved on a global scale. In fact, 
+Balakrishnan et al.  [balakrishnan03semanticfree]_ argue
+that DHTs are suitable for the next generation 
 Reference Resolutions Services (RRS) [#]_.
 
 .. [#] Domain Name System (DNS) [rfc1101]_ is a widely used RRS 




reply via email to

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