BIND 10 #2167: clarify whether to keep inmemory datasrc as a loadable module

BIND 10 Development do-not-reply at isc.org
Tue Jul 31 07:43:38 UTC 2012


#2167: clarify whether to keep inmemory datasrc as a loadable module
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  jinmei                             |                Status:  new
                       Type:         |             Milestone:  Next-Sprint-
  defect                             |  Proposed
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:  data   |           Sub-Project:  DNS
  source                             |  Estimated Difficulty:  0
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by vorner):

 Hello

 Replying to [comment:1 shane]:
 > So even if I never use the in-memory data source, I carry the code now?
 That seems like an anti-goal for bind 10. :(

 Yes. And there's the reason. The in-memory data source is used as the
 cache that can be enabled on top of any other data source. And to do that,
 the code needs some special properties of it. It uses it as the in-memory
 data source client, not as abstract data source client. And you don't get
 that out of the factory.

 Also, the static data source that is expected to be loaded every time is
 just a thin wrapper around the in-memory data source. So, actually, you
 probably use the code that is in the library now. And if it is taken out
 to a separate .so and you do use the in-memory, then you'd have it loaded
 **twice**.

 With regards

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


More information about the bind10-tickets mailing list