BIND 10 #446: configuration knob for in memory data source

[BIND 10 Development]

#446: configuration knob for in memory data source
---------------------------+------------------------------------------------
      Reporter:  jinmei    |        Owner:  vorner               
          Type:  task      |       Status:  reviewing            
      Priority:  major     |    Milestone:  y2 12 month milestone
     Component:  b10-auth  |   Resolution:                       
      Keywords:            |    Sensitive:  0                    
Estimatedhours:  0.0       |        Hours:  0                    
      Billable:  1         |   Totalhours:  0                    
      Internal:  0         |  
---------------------------+------------------------------------------------

Comment(by vorner):

 Few comments:
  - Why does destroyAuthConfigParser exist? When I saw it, I asked „Huh,
 does destroying a config parser need special attention? Why shouldn't I
 just call delete? What would go wrong?“. As I looked inside it, it does
 just that, so I think this one is only confusing. Anyway, this function
 not only should never throw, it just can't, C++ specifies that if anyone
 tries to throw out of a destructor, the application aborts.
  - Isn't it a lot to ask from commit not to throw any exception? Is it
 realistic to say that none of them will ever allocate memory, for example?

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