[Gzz-commits] manuscripts/storm link_management.txt

[Toni Alatalo]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Toni Alatalo <address@hidden>   03/01/28 01:50:21

Modified files:
        storm          : link_management.txt 

Log message:
        hyper-g notes

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/storm/link_management.txt.diff?tr1=1.5&tr2=1.6&r1=text&r2=text

Patches:
Index: manuscripts/storm/link_management.txt
diff -u manuscripts/storm/link_management.txt:1.5 
manuscripts/storm/link_management.txt:1.6
--- manuscripts/storm/link_management.txt:1.5   Mon Jan 27 16:13:05 2003
+++ manuscripts/storm/link_management.txt       Tue Jan 28 01:50:20 2003
@@ -25,6 +25,22 @@
 links (in Microcosm) relating to general content that can apppear in
 numerous specific locations [HymE-book, check e.g. 393!])
 
+(hyper-g does not seem to have location-independent identifiers, though
+haven't find a real specification yet. "Hyper-G is able to store its
+documents far more efficiently than the caching WWW proxy because it is a
+true distributed database of information. When a document is deleted,
+changed, or renamed on a server, all other Hyper-G servers that reference
+that document can be informed. This has the additional benefit of
+eliminating "dead" or moved links to information. Experienced WWW users know
+that finding references to documents that no longer exist can be quite
+frustrating. Hyper-G automatically cleans up all dead links so that the user
+no longer has to search again for the same piece of information." from
+http://www.mindspring.com/~chroma/hgc/hginfo-www.html . a paper on a
+protocol for disseminating the changes in a distributed environment is
+described in http://citeseer.nj.nec.com/kappe95scalable.html "A Scalable
+Architecture for Maintaining Referential Integrity in Distributed
+Information Systems (1995)")
+
 <COPY from="http://www.cs.aue.auc.dk/ohswg/introduction.html";>
 (http) had originally been designed to incorporate functionality for 
manipulating
 hypertexts. A "LINK" request for instance, would have allowed clients to
@@ -44,6 +60,12 @@
 quick'n'dirty html/web for now:
 note about changes the recipients derived from referer.log?
 .. what else does the go in the http, actually? (diff from spec?)
+
+from the intra-doc www9 paper:
+"Microcosm does not offer good solutions for handling them. One of their
+proposed approach prevents mutable documents from participating in links,
+and the other approach requires that documents be editing together with all
+their links."
 
 ---