BIND 10 #598: Resolver DO bit, forwarder pass DO bit

[BIND 10 Development]

#598: Resolver DO bit, forwarder pass DO bit
-------------------------------------+-------------------------------------
                 Reporter:  jreed    |                Owner:  vorner
                     Type:  defect   |               Status:  reviewing
                 Priority:  major    |            Milestone:
                Component:           |  Sprint-20110419
  resolver                           |           Resolution:
                 Keywords:           |            Sensitive:  0
Estimated Number of Hours:  0.0      |  Add Hours to Ticket:  0
                Billable?:  1        |          Total Hours:  0
                Internal?:  0        |
-------------------------------------+-------------------------------------
Changes (by zhanglikun):

 * owner:  zhanglikun => vorner


Comment:

 Replying to [comment:10 vorner]:
 > So, if I understand it correctly, the goal is to get as large answer as
 possible and truncate it if needed, but the truncation doesn't happen yet?
 So another ticket should be opened for that?

 I would like to create another ticket to support truncation(I don't know
 if we has supported the truncation in the normal recursive query, it not ,
 the new ticket will cover it also).

 > The changelog is OK regarding the code, but I'm not sure if implementing
 the simplest forwarder is in scope of this ticket. Not that I'd propose
 removing the code, if it leads towards what we want, of course.

 Well, I have chatted this with jelte and shane on jabber room, our final
 desision is do the simplest forwarder first. I would like to change the
 scope of this ticket to do it, or we can close this ticket and create a
 new ticket for implementing a simplest forwarder, what's your opinion?

 > Anyway, from the older comments, I might be little bit unclear, I meant
 changing RunningQuery→UpstreamQuery and leaving ForwardQuery as it is
 (since ForwardQuery was really good name, but the RunningQuery isn't and
 UpstreamQuery is mostly about resolver I believe).

 I would like to keep RunningQuery to decrease the workload when merging,
 there is a ticket related with refactoring RecursiveQuery, I would like to
 do the name change in that ticket.

 >
 > And is there some shared code left between the two? Or you removed
 almost everything from the forwarding version?

 Seems they have little shared code now.


 Thanks for your review.

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