BIND 10 #1803: update the RBTreeNodeChain class to identify the "previous" node
BIND 10 Development
do-not-reply at isc.org
Mon May 7 13:45:38 UTC 2012
#1803: update the RBTreeNodeChain class to identify the "previous" node
-------------------------------------+-------------------------------------
Reporter: | Owner: UnAssigned
jinmei | Status: reviewing
Type: task | Milestone:
Priority: | Sprint-20120515
medium | Resolution:
Component: data | Sensitive: 0
source | Sub-Project: DNS
Keywords: | Estimated Difficulty: 7
Defect Severity: N/A | Total Hours: 0
Feature Depending on Ticket: in- |
memory NSEC |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by vorner):
* owner: vorner => UnAssigned
* status: accepted => reviewing
Comment:
It should be ready for review. Because it was not clear to me what the
split
with #1804 should be, I just put the whole feature into the #1803 ticket.
It
doesn't seem to be that big anyway.
I didn't add the new members, I implemented it in a way similar to the
nextNode
was ‒ changing the current node_path (which would be needed anyway with
the new
members, the only difference is I destroy the last comparison result
during the
processing).
Also, bit of the code is little bit dense, but I hope the comments there
help a
little bit to explain it.
--
Ticket URL: <http://bind10.isc.org/ticket/1803#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list