Patrice, pluggable backends were implemented to satisfy the open source community's desire for flexibility, and introduced a considerable amount of administration complexity. But it made Elektra be more modularized and fancy.

We discussed before how to define a default backend, the use of environment etc, and we found that and envvar is not secure enough. The other option was to have a configuaration file for Elektra, which doesn't makes much sense for a system that wants to eliminate configuration files. Anyway, the simplest and most secure way we could think was to create a symlink.

Check the documentation for kdbOpen() and kdbOpenDefault() at http://www.libelektra.org/elektra-api/group__kdb.html

Check also this thread or the ones close to it about envvar or symlink:
http://sourceforge.net/mailarchive/forum.php?thread_id=6315777&forum_id=40176

Do you have a better idea on how to define a default backend ?

Thank you,
Avi

On 7/13/06, Patrice Dumas <[EMAIL PROTECTED]> wrote:
Hello,

Given that the selection of the default backend through a link is broken
on platforms where a proper namespace is required, I propose dropping
the libelektra-default.so link. There would still be the possibility to use
the KDB_BACKEND environment variable which seems to be more portable to
me.

(and similarly for default_dbackend).

Thoughts?

--
Pat
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Registry-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/registry-list

Reply via email to