NESTS - Named Entities in Simple Tiered Spaces

home | Entity internal structure 1 | Design objectives | Organization of namespaces | Internal implementation of namespaces | Entity internal structure 2

Entity internal (directory) structure (1)

NB: This is a temporary working document under continual revision as coding progresses. The documents and the initial implementation are co-evolving continually, so expect to find some duplications and occasional inconsistencies (all of which will be removed over time). (See page footer for most recent revision.)


Changes to the entity file structure

In an attempt to minimize the number of inodes required, a number of the variables are amalgamated into JSON structures.

The directory in which an entity is embodied may therefore contain as few as the following files:

NB, in versions up to 0.16, variables (accounts) were represented in a JSON file named .value the type of which was identified by a field named "type". In order to reduce the time (and energy) wasted unpacking/packing JSON files, the .value file has been replaced with a mutually exclusive collection of files the names of which identify the type. Whatever the type, its contents are replicated in the .history file of the currency and that of the agent accounts affected (the payer and the payee in the case of a payment) for each transaction.

These variable files include (but are not limited to):

NB: The descriptions below have not yet been fully updated.



home