Scroll to navigation

ELEKTRA-GLOSSARY(7) ELEKTRA-GLOSSARY(7)

NAME

elektra-glossary - glossary of Elektra

Introduction

customize applications towards the users needs.
makes configuration settings persistent. The application will read the configuration at every start from the configuration storage, but it is only stored if a user changes settings.
are used for configuration storages because of these constraints. They can do fast key lookups and the keys can be structured hierarchically by defining separators in the key names.
provides global access to all configuration storages of all applications in a system. Abbreviated as KDB.
is a set of libraries /src/libs/ to access configuration parameters in a global, hierarchical key database.
is a specification language /doc/METADATA.ini that allows us to describe the content of the global key database.
is a framework consisting of LibElektra, SpecElektra, and a collection of tools.
to change the application so that it uses LibElektra afterwards.
is a community that develops LibElektra, expands SpecElektra, improves Elektra´s tooling and helps to elektrify applications.

Technical Concepts

A collection of plugins to be mounted. A backend typically is responsible to read and write a configuration file.
To read the mounting configuration and mount during kdbOpen().
To consider multiple places to look for a key.
Contracts state the purpose, functionality and requirements of plugins.
To persistently and permanently include a backend in the global key database.
Allow us to have multiple keys for the same purpose and otherwise the same key name.
The unit of implementation for a feature.
Allows us to describe configuration settings.

Details

Marks keys that were changed and need to be written out to disc.
The absence of keys or values.
used in ksPop() and @ref KDB_O_POP means to remove a key from a keyset.
or abbr. del, used in keyDel(), ksDel() and @ref KDB_O_DEL means to free a key or keyset. The memory can be used for something else afterwards.
means that the key-value information in the physical database will be removed permanently.

October 2017