[bind10-dev] config experiment

[Jeremy C. Reed]

On Thu, 3 Sep 2009, Jelte Jansen wrote:

> i've just committed a little experiment for the configuration backend, 
> it's in experiments/jelte-configuration/

I built it and ran it. (Okay if I commit minor Makefile patch to help find 
boost headers?)

> Since we want to have a heavily modular system, and apart from 'have the 
> features from bind9' we don't really know what types of configuration 
> future components will need, i've been trying to make something that is 
> as flexible as possible. To achieve this, i've for now opted to make 
> something that does not really have any knowledge about what data it is 
> storing, in essence it is just a tree, where leaf nodes contain one 
> specific option, and branches represent grouped options.

I agree that it can be flexible and doesn't need to know about the data it 
will be used for.

By the way, here is another format for keeping track of properties:

NetBSD's proplib(3) which is the Property Container Object Library.
http://netbsd.gw.com/cgi-bin/man-cgi?proplib++NetBSD-current
http://netbsd.gw.com/cgi-bin/man-cgi?prop_string+3+NetBSD-current
(and follow the other links)

It is based on Apple's PropertyList but with some slight differences.
http://www.apple.com/DTDs/PropertyList-1.0.dtd
http://developer.apple.com/mac/library/documentation/Cocoa/Conceptual/PropertyLists/Introduction/Introduction.html

Examples:
http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPRuntimeConfig/Articles/ConfigFiles.html#//apple_ref/doc/uid/20002091-99507-TPXREF102
http://developer.apple.com/mac/library/documentation/Darwin/Reference/ManPages/man5/plist.5.html

I don't know if is compatible but I think so -- see the "Third party 
editing tools" via http://en.wikipedia.org/wiki/Property_list

Also see http://wiki.dragonflybsd.org/index.cgi/PropLib