Page 10 of 333
Logiweb authors write lgs files and run them through the Logiweb compiler (lgc). The lgc compiler takes an lgs file as input and produces a Logiweb reference, a Logiweb vector, a Logiweb rack, and a Logiweb rendering as output.
The rendering consists of interlinked html and pdf files and is intended for human readers. The rendering is contained in a rendering directory. The rendering directory of the combinations page is here.
In addition to the rendering, the rendering directory also contains the reference, vector, and rack of the page.
The Logiweb reference comprises about 30 bytes. It is a world wide unique identifier of the translated page. References contain a RIPEMD-160 global hash key. Having the reference of a page there are various ways of locating the vector, rack, or rendering of the page.
The lgc compiler stores the reference of a page in a file named ref.lgp under the rendering directory. The lgc compiler stores the reference in 'mixed endian hexadecimal', i.e.: bytes are in network order, each byte is written as two hex digits with the most significant hex digit first, and capital letters A to F are used for digits above 9. The Logiweb reference of the combination page is here.
The Logiweb vector of a page is a compact representation of the page suited for storing in untrusted repositories and for transmitting over untrusted networks with limited bandwidth. Having the reference of a page one can use RIPEMD-160 to verify the authenticity of the associated vector.
The lgc compiler stores the vector of a page in a file named vector.lgw under the rendering directory. The lgc compiler stores the vector in binary. The vector is not intended for human consumption.
The Logiweb rack of a page is a precompiled representation of the page suited for storing in a local cache. The lgc compiler stores the rack of a page in a file named rack.lgr in the rendering directory.
Page 10 of 333
Copyright © 2009 Klaus Grue, GRD-2009-10-01