...
| Warning |
|---|
When creating a new "free key" name, it is essential to check that it is not already present in memcached. |
When a memcached key does not directly refer to a system element but – for example – to derived quantities, the format of its format name is free and can be arbitrary defined, provided that it is not already used.
Even though the name format is arbitrary, try to keep using 8 characters names and conventional extensions it is 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 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 | _AUX | auxiliary dataset (besides _STA and _DYN) associated toGeneric data structures, not necessarily associated with a system element. | In this case it is strongly advisable that the name preceeding the _AUX extension is equal to the element name used with the _STA and _DYN extensions
(*) "J" prefix indicates that the key content is a Json document.
| Children Display |
|---|