...
When a memcached key does not directly refer to the "STA" or "DYN" fork of a system element but – for example – to derived quantities, the format of its name is free and can be arbitrary defined, provided that it is not already used.
Even though the name format is arbitrary, it is a good practice to adopt conventional extensions advisable to always use UPPERCASE and append an extension separated by a "_" (e.g. MYNEWVALMY-ARBITRARY-NAME_DAT). In any case, do not use the "_AUX" extension for a "free key".
To avoid the proliferation of extensions, try using the ones listed in the table below:
| Extension | Description | ||
|---|---|---|---|
| _ | AUXAuxiliary dataset associated to a system element (besides _STA and _DYN) . If it is necessary to add data to an element class, but it is not possible to modify the STA and DYN datasets (to keep the class compatible with the pre-existing software) it is possible to insert an additional data fork associated with the element, with the extension "_AUX". When using the "_AUX" extension, it is mandatory that the name preceeding the extension be equal to the element name preceeding the _STA and _DYN extensions. | _BUF BUF, _JBUF* | Data buffers (FIFOs , circular buffers, etc...), not necessarily associated with a system element. |
| _INFO, _JINFO* | Static metadata, not necessarily associated with a system element. | ||
| _DAT, _JDAT* | Generic data structures, not necessarily associated with a system element. |
(*) "J" prefix indicates that the key content is a Json document.
| Children Display |
|---|