Fornax Object Paradigm ...
An Estatom object is a collection of software atoms and the atom in turn is composed of the nucleus and quanta.
The nucleus is the information storage part and the building block to the atom.
Each atom can contain one, or more nucleus – i.e. nuclei. It is the mechanism for the storage of information or instructions – computer code.
The information carried in the nucleus is done in quanta. A quanta is very close to what could be termed as a ‘name’ or a ‘value’.
A nucleus (or atom) can contain data or a mixture of data and code. However, one nucleus can be a data-carrying nucleus and another can be a code-carrying nucleus.
The capabilities of the nucleus are implemented by the quanta, and with Estatom's technology there are different types of quanta, each with a specific and different role within the atom.
The nucleus is able to contain atoms or objects and this makes the system infinite in size as it allows users to build any software structure within an object.
The components of the Fornax engine are also objects, and because of the way the Fornax is designed, it provides the user with the capability to move information between different Fornax engines regardless of the hardware platform and configuration.
Another feature of Fornax, and its object-based approach, is that the execution of the nucleus within an object only needs an object environment to function. It does not use the system stack, therefore an object can move from one machine to another machine, even while it is executing.
The lattice or collection of objects that forms an application or solution can comprise objects that reside on different machines, therefore every object must have a unique identifier, and every atom and every nucleus within the object must also have a unique identifier. This allows a user to add data or variables carried in one nucleus on one machine in one object, to nuclei on another machine in a different object, or a copied object or a completely new object, all on another machine.
Estatom's objects are self-contained, coded without reference to a physical machine, and carry all the information that is required to function within itself independently.
To run the program on a computer, or device, the user must use a Fornax engine. The Fornax engine which the user runs, must be configured, or suitable, for the particular machine to be used because the Fornax engine is coded to fit the processor of that machine, as well as the Operating System. However, it is possible to run Fornax without an Operating System.
The Fornax engine has a set of internal rules and processes for security. The engine will force any object to look at access control, encryption and ownership before it even attempts to process the object further.
All information in Fornax is stored in object form, and all Fornaxes are themselves running in object form.
Estatom's object structure is configurable, so a programmer or user is able to construct a Fornax engine as required. Therefore, a Fornax can be configured and tuned to fit a particular application or purpose. This engine programmability is outside of any application programmability.
Estatom objects are machine independent, but the execution of a program (also objects), is via the Fornax engine, and is brought down to the exact format required for the processor. This means that an application only has to be written once, and then it can be run everywhere, and it does not require any recompilation, linking, tuning or conversion.