[bind10-dev] datasource list vs zone list

[Evan Hunt]

> On the datasource call, a topic came up that is sort of interesting.
> Namely, how do we do the mapping from zone name to datasource?  Also,
> can multiple DSs take a stab at an answer and say they do not handle
> that zone, try the next one?

I don't have a lot to add to this conversation, but I wanted to share a
thought that occurred to me as I was reading through it:  This reminds
me of a) views, and b) recursive resolvers.

To implement views, we'll need to be able to have a given name stored
in more than one place (either two different versions in a single data
source, or two different data sources each containing $name) (or maybe
even both).  The final answer would have to be chosen on the basis of
query characteristics.

To implement a recursive resolver, we'll need to be able to pull data
from the cache, and in the event of a cache miss, do the whole fetch/
validate dance.  If you consider the latter to be a kind of "virtual
data source", then that's two data sources being accessed in series.

So it strikes me that might be useful and instructive to consder the
data source issue in the context of these other things, because it's
likely to be a piece of the solution we come up for those as well.

                                        eh