Difference between revisions of "Node space"
From Organic Design wiki
(add image) |
m |
||
| Line 12: | Line 12: | ||
;See also | ;See also | ||
*[[Nodal Reduction]] | *[[Nodal Reduction]] | ||
| − | *[[husk.c]] impliments the functional way from the [[List Space]] level. | + | *[[husk.c]]/[[nodeSpace.c]] impliments the functional way from the [[List Space]] level. |
*[[nodal-wikid.pl]] extends PERL's native hash-table to make a Nodal Space. | *[[nodal-wikid.pl]] extends PERL's native hash-table to make a Nodal Space. | ||
*[[peer-nodal.as]] impliments the functional way since ECMA can't use references as array-keys. | *[[peer-nodal.as]] impliments the functional way since ECMA can't use references as array-keys. | ||
Revision as of 08:50, 8 August 2006
A Nodal Space is a local collection of nodes existing on a Peer at runtime to which the Nodal Reduction process occurs. All nodes at runtime are referred to directly by their memory references, not by their global identity which is only used for storage and communication of nodal information, not the processing of it.
On languages that support it, a Nodal Space can be implimented by sub-classing the standard associative array syntax and methods to allow the use of associative-array-references as array-keys rather than strings or numbers.
For languages that don't support this level of object-orientedness, the Nodal Space must be implimented using functions or methods with a list of associative-array-references as a path parameter.
- See also
- Nodal Reduction
- husk.c/nodeSpace.c impliments the functional way from the List Space level.
- nodal-wikid.pl extends PERL's native hash-table to make a Nodal Space.
- peer-nodal.as impliments the functional way since ECMA can't use references as array-keys.
