\hypertarget{struct__Backend}{
\section{\_\-Backend Struct Reference}
\label{struct__Backend}\index{\_\-Backend@{\_\-Backend}}
}


{\ttfamily \#include $<$kdbprivate.h$>$}



Collaboration diagram for \_\-Backend:
\nopagebreak
\begin{figure}[H]
\begin{center}
\leavevmode
\includegraphics[width=188pt]{struct__Backend__coll__graph}
\end{center}
\end{figure}
\subsection*{Data Fields}
\begin{DoxyCompactItemize}
\item 
\hyperlink{struct__Key}{Key} $\ast$ \hyperlink{struct__Backend_a5494dade5125f76ef8d77a24cdec1f84}{mountpoint}
\item 
ssize\_\-t \hyperlink{struct__Backend_a86eba6e73242d79efed2a313d25bdd76}{usersize}
\item 
ssize\_\-t \hyperlink{struct__Backend_a0af9c2bc4e327a17df20de41918d34cc}{systemsize}
\item 
size\_\-t \hyperlink{struct__Backend_a033b9df8d33fd2575bf26818fcce5bb4}{refcounter}
\end{DoxyCompactItemize}


\subsection{Detailed Description}
Holds all information related to a backend.

Since Elektra 0.8 a Backend consists of many plugins. A backend is responsible for everything related to the process of writing out or reading in configuration.

So this holds a list of set and get plugins.

Backends are put together through the configuration in system/elektra/mountpoints

See kdb mount tool to mount new backends.

To develop a backend you have first to develop plugins and describe through dependencies how they belong together. 

\subsection{Field Documentation}
\hypertarget{struct__Backend_a5494dade5125f76ef8d77a24cdec1f84}{
\index{\_\-Backend@{\_\-Backend}!mountpoint@{mountpoint}}
\index{mountpoint@{mountpoint}!_Backend@{\_\-Backend}}
\subsubsection[{mountpoint}]{\setlength{\rightskip}{0pt plus 5cm}{\bf Key}$\ast$ {\bf \_\-Backend::mountpoint}}}
\label{struct__Backend_a5494dade5125f76ef8d77a24cdec1f84}
The mountpoint where the backend resides. The \hyperlink{group__keyname_ga8e805c726a60da921d3736cda7813513}{keyName()} is the point where the backend was mounted. The \hyperlink{group__keyvalue_ga6f29609c5da53c6dc26a98678d5752af}{keyValue()} is the name of the backend without pre/postfix, e.g. filesys. \hypertarget{struct__Backend_a033b9df8d33fd2575bf26818fcce5bb4}{
\index{\_\-Backend@{\_\-Backend}!refcounter@{refcounter}}
\index{refcounter@{refcounter}!_Backend@{\_\-Backend}}
\subsubsection[{refcounter}]{\setlength{\rightskip}{0pt plus 5cm}size\_\-t {\bf \_\-Backend::refcounter}}}
\label{struct__Backend_a033b9df8d33fd2575bf26818fcce5bb4}
This refcounter shows how often the backend is used. Not cascading or default backends have 1 in it. More than two is not possible, because a backend can be only mounted in system and user each once. \hypertarget{struct__Backend_a0af9c2bc4e327a17df20de41918d34cc}{
\index{\_\-Backend@{\_\-Backend}!systemsize@{systemsize}}
\index{systemsize@{systemsize}!_Backend@{\_\-Backend}}
\subsubsection[{systemsize}]{\setlength{\rightskip}{0pt plus 5cm}ssize\_\-t {\bf \_\-Backend::systemsize}}}
\label{struct__Backend_a0af9c2bc4e327a17df20de41918d34cc}
The size of the systems key from the previous get. Needed to know if a key was removed from a keyset. \hypertarget{struct__Backend_a86eba6e73242d79efed2a313d25bdd76}{
\index{\_\-Backend@{\_\-Backend}!usersize@{usersize}}
\index{usersize@{usersize}!_Backend@{\_\-Backend}}
\subsubsection[{usersize}]{\setlength{\rightskip}{0pt plus 5cm}ssize\_\-t {\bf \_\-Backend::usersize}}}
\label{struct__Backend_a86eba6e73242d79efed2a313d25bdd76}
The size of the users key from the previous get. Needed to know if a key was removed from a keyset. 

The documentation for this struct was generated from the following file:\begin{DoxyCompactItemize}
\item 
kdbprivate.h\end{DoxyCompactItemize}
