Commit 62dfb928 authored by JINMEI Tatuya's avatar JINMEI Tatuya
Browse files

updated the the Zone class description with future possible plans of...

updated the the Zone class description with future possible plans of interaction with other data sources.  based on a follow-up discussion in code review.

git-svn-id: svn:// e5f2f494-b856-4b98-b285-d166d9295462
parent b645455b
......@@ -45,6 +45,18 @@ namespace datasrc {
/// information about the location of a zone file, whether it's loaded in
/// memory, etc.
/// It's not yet clear how the derived zone classes work with various other
/// data sources when we integrate these components, but one possibility is
/// something like this:
/// - If the underlying database such as some variant of SQL doesn't have an
/// explicit representation of zones (as part of public interface), we can
/// probably use a "default" zone class that simply encapsulates the
/// corresponding data source and calls a common "find" like method.
/// - Some data source may want to specialize it by inheritance as an
/// optimization. For example, in the current schema design of the sqlite3
/// data source, its (derived) zone class would contain the information of
/// the "zone ID".
/// <b>Note:</b> Unlike some other abstract base classes we don't name the
/// class beginning with "Abstract". This is because we want to have
/// commonly used definitions such as \c Result and \c ZonePtr, and we want
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment