New configuration backends for Samba 3 SoC project

[Stefan (metze) Metzmacher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ming schrieb:
> 2006/5/28, Gerald (Jerry) Carter <jerry at samba.org>:
>> In order to meet the speed requirement,heavily accessed option should
>> use in-ram hashes.Is it possible to implement an architecture as:
>> +---------------------------------------+
>> |parameter access interface |
>> +---------------------------------------+
>>                     |
>> +-----------------------+ +-----------+
>> |smb.conf parser |   | LDB     |
>> +-----------------------+ +-----------+
>> We define a set of new interface which text configuration and LDB
>> configuration modules should implement(other futhure one conform to it
>> too).
Hi Ming,

This sounds like the approach we should use.

And the interface should use a context structure that needs to be passed
to each function, so that we get rid of global var (or for a first step
hide them in the smb.conf backend).

As a side effect this would allow us to have different config contexts
for different things...(maybe usefull in samba4 later).

I had a quick look at the www.libelektra.org the gui looks very nice a
bit like the windows registry editor:-) But I think we should not depend
on it in samba...

What we could do is orient our interface on the lelektra one, so that
writting an libelektra-samba.so would be just wrapping our interface.

So admin tools can access via the elektra interface, but samba directly
uses its own interface.

metze
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFEfHiSm70gjA5TCD8RAutNAJ49g+x6t/0/twmXaVc82kWSu9w4iwCfVisL
4a3qIdyxO+459mLEz0DQcsc=
=IbIh
-----END PGP SIGNATURE-----