|Page 408 of 800||Search internet|
As mentioned, when 'loading' a Logiweb reference one obtains a Logiweb 'cache'. Loading a reference is univocal, so loading a reference twice gives the same cache both times.
Loading a reference may require quite some computational resources, so it is reasonable to avoid loading the same reference twice.
The cache of a page is an array which maps cardinals to values. The cache of a page maps the cardinal 0 to the reference cardinal of the page itself. Furthermore, the cache of a page maps the reference cardinals of the page and all its transitively referenced pages to the 'racks' of each page.
The 'rack' of a page is another array which maps cardinals to values. We refer to an array of inhomogeneous data as a 'rack' and to the indexes of such an array as 'hooks'. The hooks are strings like 'bibliography' and 'dictionary' converted to cardinals.
The rack of a page maps the bibliography hook to the bibliography of the page, the dictionary hook to the dictionary of the page, and so on. The rack of a page has the following hooks:
One purpose of caches is to avoid loading the same reference more than once. Another is that the cache of a page constitutes the well-defined subset of the entire Logiweb that is needed for codifying, verifying, executing, and rendering the page.
To unpack a page one has, among other, to load all proper entries in the bibliography of the page. Loading those entries involves unpacking which may require further pages to by loaded and so on. Hence, unpacking a page includes loading all pages reachable from the page through bibliographic references. The process stops when reaching 'base' pages which are pages with no proper bibliographic entries.
|Page 408 of 800||Search logiweb.eu|