BIND 10 #810: TSIG: Create non-module config location support
BIND 10 Development
do-not-reply at isc.org
Wed Apr 13 12:39:04 UTC 2011
#810: TSIG: Create non-module config location support
-------------------------------------+-------------------------------------
Reporter: stephen | Owner: UnAssigned
Type: | Status: reviewing
enhancement | Milestone:
Priority: blocker | Sprint-20110419
Component: | Resolution:
Unclassified | Sensitive: 0
Keywords: | Add Hours to Ticket: 0
Estimated Number of Hours: 2.0 | Total Hours: 0
Billable?: 1 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jelte):
BTW, I think we should consider moving all .spec files out of their
modules directory, and put them all together in one dir in the source tree
(similar to how they end up when installed), cfgmgr could then load them
all at once (we also need something like that for 'offline'
configuration). This could then also be the place for specs that have no
actual module associated with them. Perhaps the specfile itself could then
specify whether there is a module they belong to, it has some loadable
dynamic checking code, or no checking apart from syntax at all.
Right now, modules can 'spy' on other module's configs with the 'remote
config' set of functions; these are 'secretly' updated when configuration
changes occur, and modules that listen to the configs of others don't
react to them. (Due to the current implementation, they also get no
module-level signal when it changes; they should access the config data
directly, and not copy it for efficiency; the underlying config values are
silently updated)
--
Ticket URL: <http://bind10.isc.org/ticket/810#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list