BIND 10 #1788: update auth spec to specify in-memory "filetype" with sqlite3 backend

[BIND 10 Development]

#1788: update auth spec to specify in-memory "filetype" with sqlite3 backend
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20120417
  medium                             |            Resolution:
                  Component:         |             Sensitive:  0
  b10-auth                           |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  3
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:  xfr    |
  for in-memory                      |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => jinmei


Comment:

 I have few small things:
  * While this is out of the scope of this ticket, I believe we could use
 an „enum“ config type. It would be a nicely dressed string, but with only
 a list of allowed values checked even in bindctl and with tam completion.
 This is another place it would be useful. Would you mind if I create one?
  * Should the tests also check the `errors_` list is empty?
  * The `699f21c00c5136c0128cfbb842c1d3218de11cfe` commit might have had a
 better message (as we talked last week on the call). It's probably not
 worth fixing now, but some future ones might want to hint tests for what
 these are in the body of the message.
  * I don't think „optional“ goes very well together with „default“.
 Optional means the option may or may not be present at all (therefore it
 would have _no_ value). The default is that the option is there all the
 time, but it has this value if not set. The combination of both leads to
 the fact the default must be hardcoded in the code, which is bad (the
 default is at two different places). Do you think it would be possible to
 make it non-optional and have a default value?

-- 
Ticket URL: <http://bind10.isc.org/ticket/1788#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development