...
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 | ||
---|---|---|---|
_BUF, _BUF JBUF* | Data buffers (FIFOs , circular buffers, etc...) | _AUX | Auxiliary dataset (besides _STA and _DYN) associated to , not necessarily associated with a system element.When using the "_AUX" extension, it is strongly advisable that the name preceeding the extension be equal to the element name used besides the _STA and _DYN extensions. |
_INFO, _JINFO* | _INFO | 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 |
---|