[Gzz-commits] manuscripts/pointers article.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Tuomas J. Lukka <address@hidden>        03/11/02 15:02:07

Modified files:
        pointers       : article.rst 

Log message:
        formattingupdates

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/pointers/article.rst.diff?tr1=1.82&tr2=1.83&r1=text&r2=text

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.82 
manuscripts/pointers/article.rst:1.83
--- manuscripts/pointers/article.rst:1.82       Sun Nov  2 14:54:51 2003
+++ manuscripts/pointers/article.rst    Sun Nov  2 15:02:07 2003
@@ -431,20 +431,22 @@
 As an example of a different application,
 pointer records could be used to implement
 a p2p version of software upgrades
-such as Debian's ``apt`` or Windows update.
-This could yield large bandwidth savings
-with the additional benefit of being able to
-(due to the simple underlying model requiring
-only the blocks)
-for example burn the new versions and their pointers to a CD
-to take to a machine that is not connected
-to a network.
+such as Debian's ``apt`` or Windows update,
+allowing large bandwidth savings.
 
-XXX Onion ref?
+An important feature of pointer records, due
+to the simple underlying block abstraction, is
+that it is possible to
+for example burn the new versions of packages
+(and their pointers records) to a CD
+to take to a machine that is not connected
+to a network. Because the versioning model only
+uses the pointer blocks as data, the software upgrade
+should simply work out in such a case.
 
-versioning
-  is also distributed - no central server needed
-  for distributor
+XXX Onion ref?  versioning
+is also distributed - no central server needed
+for distributor
 
 
 Implementation