[bind10-dev] config data api

[Jelte Jansen]

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

On 04/13/2012 09:44 AM, Michal 'vorner' Vaner wrote:
> Hello
> 
> So, few more promised comments:
> 
> On Thu, Apr 12, 2012 at 04:38:07PM +0200, Jelte Jansen wrote:
>> So, initial requirements braindump:
> 
> I'm not sure if this might or not be useful, but would it make
> sense to be able to place module as a sub-module/subpath of some
> other module? We have a microsoftish approach now (eg. we have
> top-level „drives“), would it make sense to make it unixish
> (mounting everywhere is allowed)? It would make sense for some
> plugins not to be configured completely separately.
> 

i suspect that this would be needlessly complicated, both in terms of
implementation and in use; if you update one value you wouldn't expect
a seemingly 'remote' value to be change as well.

We could use some way to 'define' complex types though (acls come to
mind), or a standard way to point to them.

But mount-like features seem unnecessary to me, as long as we can
address anything, and not just the modules own data

>> - - start extending our types, and maybe even add custom
>> syntactic requirements to elements from the specification (this
>> has been a plan before, but never materialized)
> 
> Would the types have some kind of Element subclass each, maybe
> registered somewhere dynamically (so a plugin/new module can add
> its own without changing the whole library)?
> 

...and this is a point where i wish we had done everything in python,
and *only* do critical-code-paths in c++ as python modules. In which
case the answer would've been yes. As it stands, we could, but I'm not
sure whether adding yet another loadable module point would be worth it.

(hmm, unless we revisit the idea to make every component a loadable
module, with run(), checkConfig() calls, etc. Then there may be an
easy way to add this to it)

Jelte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+H7LIACgkQ4nZCKsdOncWXGQCgh+VXgjRoEIqj3XZ3yuIkyLG4
NhkAoLipdcJ7Yhq/nmHwJErTPeJywJcz
=SrPF
-----END PGP SIGNATURE-----