BIND 10 #2427: support $ORIGIN in dns::MasterLoader

BIND 10 Development do-not-reply at isc.org
Thu Dec 20 03:45:27 UTC 2012


#2427: support $ORIGIN in dns::MasterLoader
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  task          |  vorner
            Priority:  medium        |                       Status:
           Component:  libdns++      |  closed
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20121218
         Sub-Project:  DNS           |                   Resolution:
Estimated Difficulty:  3             |  complete
         Total Hours:  0             |                 CVSS Scoring:
                                     |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |  loadzone-ng
                                     |          Add Hours to Ticket:  8.99
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:18 vorner]:

 > But, once again, I found a problem in lexer. I was wondering, wouldn't
 it be
 > more correct to create a new lexer for each of the input sources instead
 of
 > using the same one for all of them?

 It depends on what kind of state we want to bring to the pushed
 source, but maybe.  I don't see the strong need for changing the
 current implementation, though.  The interface between the loader and
 lexer is mostly private, so if and when see specific reason for
 changing it we can do it without affecting actual users of the
 library.

 > And, also, I was wondering, we have a logging system which can be
 translated.
 > But these messages from the loader won't be. Isn't it a problem?

 Yeah good point, I was aware of that, too, but forgot it almost
 immediately:-)  I agree that the current approach is not ideal but I
 don't have an immediate nice solution to that.

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


More information about the bind10-tickets mailing list