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

[BIND 10 Development]

#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 jinmei):

 Replying to [comment:1 shane]:
 > So even if I never use the in-memory data source, I carry the code
 > now?

 Regarding *now*, yes, because libdatasrc includes memory_datasrc.o.

 But note the 'if' in the ticket description.  The main background
 point of this ticket is that it doesn't make sense we have the
 memory_datasrc code in libdatasrc while generating memory_ds.so.

 We should first decide whether we keep the in-memory implementation a
 loadable module or include it it in libdatasrc.  If it's the former,
 we should remove it from the library; if it's the latter, we should
 stop generating the loadable module.

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