[bind10-dev] Datasources, meta-datasource and configuration

[JINMEI Tatuya / 神明達哉]

At Wed, 18 Apr 2012 13:24:16 +0200,
Michal 'vorner' Vaner <michal.vaner at nic.cz> wrote:

> First, I see several requirements around this:
>  • We need a possibility to describe different data sources in the
>    configuration (different types or just different sqlite3 files or whatever).
>  • Multiple components need access to them.
>  • Describe a way to cache some zones from some data sources to in-memory in
>    auth, but not do it in xfrin/out/ddns.
>  • Describe behaviour of finding the right zone to answer.
>  • Aggregate the data sources together and be able to chose the right one.
>  • Share the code across all modules that need it.

These requirements look reasonable.  I think the example configuration
generally makes sense too.  Some preliminary comments:

- As we discussed in the msgq-ng context I'm not sure if it's
  reasonable to enumerate all in-memory zones in this configuration.
  Maybe a good topic for the f2f meeting.
- in-memory could be also used for xfrout (using AXFR) as long as it
  provides the iterator interface.
- maybe it's too early to talk about the implementation, but
  personally I'm not convinced that the best way to implement it is to
  make the "meta datasource" as an interchangable derived class with
  other data source (client) classes.
- I'm not sure if I understand the "single match" type usage.  But in
  any event, I guess it's subject to discussion how we realize that
  different components can prefer/exclude particular types of data
  sources.

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.