<br><br><div><span class="gmail_quote">On 4/18/05, <b class="gmail_sendername">Magnus Bergman</b> <<a href="mailto:magnus.bergman@observer.net">magnus.bergman@observer.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>The solution is to have the same API for communication with the daemon<br>as for communication with the back-ends directly. This is simply done by<br>using the same library. What the library does is to decide which<br>
back-ends to use and when. This functionality is used by both<br>application and the daemon, so they link to the same library and use the<br>same API. But only the daemon uses the library to call the back-ends<br>which needs the daemon.
<br><br> ,----------------------,<br> |
Daemon-link back-end |<br> ,-------------, ,---------,/`----------------------'<br> | Application |--| Library |<br> `-------------' `---------'\,----------------------,<br> |
Some other back-ends |<br> `----------------------'<br><br> ,--------, ,---------, ,------------------------------,<br> | Daemon |--| Library |--| Back-ends needing the daemon |<br> `--------' `---------' `------------------------------'
</blockquote></div><br>
You can implement the backend access of Elektra as "backend access through daemon".<br>
See <a href="http://elektra.sourceforge.net/elektra-api/html/group__backend.html#ga8">http://elektra.sourceforge.net/elektra-api/html/group__backend.html#ga8</a><br>
<br>
Avi<br>