[bind10-dev] config data api

Jelte Jansen jelte at isc.org
Fri Apr 13 08:56:48 UTC 2012


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

On 04/12/2012 07:09 PM, Michal 'vorner' Vaner wrote:
> 
> This sounds you want to replace both the specifications and the
> actual data with classes. I find it really user friendly the data
> itself (parameters to commands, configs, etc) are the raw python
> primitives, as they are much easier to handle.
> 

Yes that was part of the idea, though I was thinking of having a
getValue-like call in the that returns the primitives for this.

> We probably could make the lists iterable and the maps [ ]
> indexable, etc, but is there really a need? Or can the dict/list be
> inherited to add some more functionality to them?
> 

AFAIK, you can assign anything to anything in python, except to
primitives, so no. But we could indeed duck-type their primitives'
behaviour on top of these. Not sure if we should, though, it would add
a lot of potentially confusing implicitness.

We can of course start out by skipping all of this and just doing the
specifications classes and see if that makes it all easy enough :)

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

iEYEARECAAYFAk+H6lAACgkQ4nZCKsdOncXbNwCfeuOH5wGExNBveeLt4avgTd7x
NMIAn1lYsiZldpofg6AceIpzwINhj36s
=J5vk
-----END PGP SIGNATURE-----


More information about the bind10-dev mailing list