[bind10-dev] datasources config

[Jelte Jansen]

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

On 09/26/2011 08:56 PM, JINMEI Tatuya / 神明達哉 wrote:
>>
>> Just to make sure I get the idea here, so in effect a client like auth
>> would see that for an IN query, it needs to check inmemory and sqlite3,
>> it then takes the global configs for those and sets up clients?
> 
> "In effect", yes.  (From the API point of view it would be hidden in
> the polymorphic factory).
> 

not completely, or well, there could be helper functions for such things
but i'd let actual control be the responsibility of the caller ("I want
you, InMemory, with these settings" "Now I want you to change it to
these", as opposed to "Here is access to the entire system, give me what
you think I need"). But this is an implementation detail as far as where
the calls lie within the various modules, not which are needed.

> 
> The use case I was thinking about is that auth and xfrin would
> probably use different sets of data sources.  Specifically, auth
> would only need read-only interfaces (and preferably efficient ones),
> so it would primarily use the inmemory client (sqlite3 was included in
> the above example just in case).  On the other hand, xfrin needs
> writability (but the access speed can be much slower) so the inmemory
> client is of no use for it.
> 

Having a xfrin talk to a datasource that isn't used by any form of auth
or xfrout will not be really useful :)

But I get your point, not all modules may need all of them (a read-only
ds will never be useful for xfrin or dyn, but I can probably think of a
few less fundamental usecases), so yeah, this is probably a good idea.

> Such characteristics are local to each application (auth, xfr-in/out,
> update, etc), so I thought it would be more natural to give the
> application right to choose necessary interfaces.
> 
> But in any event, these are preliminary thoughts mainly as food for
> discussion, rather than a strong opinion.
> 

I think we are not having enough of those lately, so I applaud them :)

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

iEYEARECAAYFAk6A/F4ACgkQ4nZCKsdOncW7fgCg0piex+6R+lyBLiH0LWN9m33j
kvgAnAg1VRT0v2jAJ8Z/BMnX0V0/liPk
=8tHw
-----END PGP SIGNATURE-----