[bind10-dev] multiple datasources with the new API

[Michal 'vorner' Vaner]

Hello

I always envisioned a metadatasource, that would:
• Go in the order in the configuration. This means user can place the in-memory
  first for the „busy“ zones and leave the less busy in DB and most of the answers
  would be answered from memory. If we went for best match, we would need to
  consult all of the sources to decide. If we wanted to do something smart, then
  it would turn out to be too smart in some cases (which I personally really hate
  about computers, if they think they're smart) and complicated.
• It would just try calling the getZoneIterator/getZoneFinder/getZoneUpdater (or
  how the methods are named) and if it gives an answer, just return it. If it
  doesn't, moves to the next data source. This makes it quite easy to implement
  it.

I'd like to go the metadatasource way instead of hardcoding this try each one in
a row into auth, for two reasons. One, if there's only one data source
configured, the whole machinery of each-one-in-a-row can be avoided. Other, more
important, there are other things than auth that will need to handle multiple
data sources. We shouldn't need to write the try each one multiple times, once
for auth, once for xfrout, once for xfrin, once for resolver (if we go the way
with local zones).

With regards

-- 
Commenting perl code is useless. You have to fully parse it anyway to find comments.

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20111008/9cee9f4a/attachment.bin>