BIND 10 #458: Additional MX processing

[BIND 10 Development]

#458: Additional MX processing
-------------------------------+--------------------------------------------
      Reporter:  vorner        |        Owner:  vorner   
          Type:  task          |       Status:  reviewing
      Priority:  major         |    Milestone:           
     Component:  Unclassified  |   Resolution:           
      Keywords:                |    Sensitive:  0        
Estimatedhours:  0.0           |        Hours:  0        
      Billable:  1             |   Totalhours:  0        
      Internal:  0             |  
-------------------------------+--------------------------------------------

Comment(by vorner):

 Replying to [comment:4 jinmei]:

 > '''Query::process() modification'''
 >  - the Zone::SUCCESS case block is getting large, and since it's quite
 likely to support more additional cases, we'll need to move it to a
 separate method.  I don't necessarily request it for this particular
 ticket for now, though.

 It seems the code of NS additional processing is much cleaner than this
 and a lot of it can be used. I'll wait for it to get merged and then I'll
 update it to take advantage of that.

 >  - why do you perform recursive query calls to look up the additional
 RRsets?  From a quick look at the code with some local experiments, it
 could simply be something like this:

 I wasn't sure if CNAME chasing and so on should happen or not. You mention
 it shouldn't, so this kind will be sufficient.

 >  beside, if we only care about the number of RR(set)s, I'd simply use
 Message::getRRCount().

 Hmm, I would have to put an RR into the RRset. Otherwise, it returns 0, as
 this one is empty.

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