When creating a new key, it is essential to check that it is not already present in memcached.
| Extension | Description |
|---|---|
| _STA, _JSTA* | Static and dynamic dataset forks associated with a system element. Usually, memcached canonical keys are generated by DEVILs and directly associated with a system element (e.g. QUATB004). These canonical keys take the same name of the element with two possible extensions: "_STA" and "_DYN". If the class is new (and consequentely not used by pre-existing software), its content can also be written as a Json document; in this case it is good practice to use the "_JSTA" and "_JDYN"extensions. |
| _DYN, _JDYN* | |
| _AUX, _JAUX* | Auxiliary dataset fork associated with 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 format (to keep the class compatible with 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. Beeing the _AUX fork new by definition (and consequentely not used by pre-existing software), its content can also be written as a Json document; in this case it is good practice to use the "_JAUX" extension. |
(*) "J" prefix indicates that the key content is a Json document.