| … | |
… | |
| 889 | contains values. |
889 | contains values. |
| 890 | |
890 | |
| 891 | The top level hash key is called "family", and the second-level hash key |
891 | The top level hash key is called "family", and the second-level hash key |
| 892 | is simply called "key". |
892 | is simply called "key". |
| 893 | |
893 | |
| 894 | The family and key must be alphanumeric ASCII strings, i.e. start |
894 | The family must be alphanumeric, i.e. start with a letter and consist |
| 895 | with a letter and consist of letters, digits, underscores and colons |
895 | of letters, digits, underscores and colons (C<[A-Za-z][A-Za-z0-9_:]*>, |
| 896 | (C<[A-Za-z][A-Za-z0-9_:]*>, pretty much like Perl module names. |
896 | pretty much like Perl module names. |
| 897 | |
897 | |
| 898 | As the family namespaceis global, it is recommended to prefix family names |
898 | As the family namespace is global, it is recommended to prefix family names |
| 899 | with the name of the application or module using it. |
899 | with the name of the application or module using it. |
| 900 | |
900 | |
|
|
901 | The keys must be strings, with no other limitations. |
|
|
902 | |
| 901 | The values should preferably be strings, but other perl scalars should |
903 | The values should preferably be strings, but other perl scalars should |
| 902 | work as well (such as arrays and hashes). |
904 | work as well (such as undef, arrays and hashes). |
| 903 | |
905 | |
| 904 | Every database entry is owned by one node - adding the same family/key |
906 | Every database entry is owned by one node - adding the same family/key |
| 905 | combination on multiple nodes will not cause discomfort for AnyEvent::MP, |
907 | combination on multiple nodes will not cause discomfort for AnyEvent::MP, |
| 906 | but the result might be nondeterministic, i.e. the key might have |
908 | but the result might be nondeterministic, i.e. the key might have |
| 907 | different values on different nodes. |
909 | different values on different nodes. |
