Difference between revisions of "State"
From Organic Design wiki
(George ought to help out) |
|||
| Line 1: | Line 1: | ||
| − | + | All [[node]]s can have non-nodal content like file-handles or objects associated with them similar to the way emails can have non-plain-text data as attchments. Every node exhibits such a ''state'' which is its encapsulation of the concept it represents ''in terms of the local [[Wikipedia:Runtime|runtime]] environment''. If the node has no representation in terms of the local environment, then a request of its state returns the local representation of ''void''. | |
The [[peerd.c]] implementation maintains a list of pointers (the ''**pointers'' global variable) to non-nodal content. Node's values can be used as an index into the pointer list instead of as a [[node reference]]. | The [[peerd.c]] implementation maintains a list of pointers (the ''**pointers'' global variable) to non-nodal content. Node's values can be used as an index into the pointer list instead of as a [[node reference]]. | ||
[[Category:Nodal Concepts]] | [[Category:Nodal Concepts]] | ||
Revision as of 14:16, 24 July 2012
All nodes can have non-nodal content like file-handles or objects associated with them similar to the way emails can have non-plain-text data as attchments. Every node exhibits such a state which is its encapsulation of the concept it represents in terms of the local runtime environment. If the node has no representation in terms of the local environment, then a request of its state returns the local representation of void.
The peerd.c implementation maintains a list of pointers (the **pointers global variable) to non-nodal content. Node's values can be used as an index into the pointer list instead of as a node reference.
