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

[Benja Fallenstein]

Toni Alatalo wrote:
> +.. tried to think this a bit, as 'never' is always a strong word.
> +   can it be that data in the cache is 'out-of-sync', i.e. 
> +   there are different versions so that links indeed break for 
> +   off-line browsing? e.g. when there is document A linking 
> +   to document B, both v1.0, and the user downloads them. then,
> +   both are updated on the server, to versions 1.1. user dowloads
> +   A, goes off-line, and tries to follow the link to B(1.1?). ? 
> +   i know this is not what is meant above, but yet an example of how 
> +   evil reviewers might react to the strong notion 'never' there ;o
> +   or is it so that the link from A to B is not to a particular version,
> +   but to any B, so that in that case the user would get B1.0 and be happy?
> +   (or confused, if diff from A,B1.0->1.1 was so major that how A1.1 links to
> +   B1.1 does not make any sense when the user ends up in 1.0 instead?)
> +   -- antont

Think again :-) -- we're talking references to *immutable* blocks here, 
which means neither the source nor the target *can* change at this 
level. Should make this clearer in the text tho; the *real* kind of 
links we use are Xu links and things are subtly different there again 
(you find the newest version you have locally, usually; the general rule 
is: any known current version of any document that transcludes the 
linked bytes-- I guess).

-b.