| Warning |
|---|
When creating a new key, it is essential to check that it is not already present in memcached. |
When a memcached key does not directly refer to the "_STA" or "_DYN"dataset of a system element but – for example – to derived quantities, the format of its name is free and can be arbitrary defined, it takes a name of 8 characters followed by a 3 characters provided that it is not already used.
Even though the name format is arbitrary, it is advisable to always use UPPERCASE and append an extension separated by a "_" . Both the name and the extension are arbitrary even though It's advisable use 8 characters names and conventional extensions (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, _ | DATgeneric data structures | _EXT | extra data associated to a _STA or _DYN datasetJINFO* | 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 |
|---|