[bind10-dev] How to organize zone config items in bind10?

[Shane Kerr]

Likun,

On Tue, 2010-08-03 at 21:10 +0800, ZhangLikun wrote:
> There are several config items for one zone,  master_addr, also_notify,
> allow_update, etc.  Since the items are used by different modules, so it
> makes sense to distribute these config items to different modules, like:
> 
> Xfrin has config item: master_addr
> Xfrout has config item: also_notify
> Update has config item: allow_update
> 
> And bind10 also need one "zone_list" config item, to make clear which zones
> bind10 is servicing, my suggestion is let config manager module hold the
> config item 'zone_list'. 
> 
> My question is : does it need to let config manager hold all the config
> option for one zone? So that the duplicated zone list information can be
> avoided in xfrin, xfrout and other modules. Like, config manager will have
> the config data like:
>     Zones :  [
> 	 { 'cn' :  [  {  ' master':  [master_list]  }, 
>                {  'also_notify' :  [notify_slave_list]  },
>                {  'allow_update' :  [address_list]  }, 
> 		      .... some_other_options....
>             ]
>       
>       'com'  :  [  ...zone's_options.... ]
>       'net' :  [  ...zone's_options.... ]
>      }
> 
> Any suggestion?

Hopefully I did not miss a discussion about this. :-P

In any case, avoiding duplication makes sense to me. I think it is okay
for modules to use configuration for "other" modules, as long as this is
done in a controlled way.

--
Shane