BIND 10 #2432: define and implement base and libdns++ version of RRsetCollection

BIND 10 Development do-not-reply at isc.org
Fri Jan 4 10:56:37 UTC 2013


#2432: define and implement base and libdns++ version of RRsetCollection
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  task          |  vorner
            Priority:  medium        |                       Status:
           Component:  libdns++      |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20130108
         Sub-Project:  DNS           |                   Resolution:
Estimated Difficulty:  5             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |  loadzone-ng
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:  muks => vorner


Comment:

 Replying to [comment:28 jinmei]:
 > It's certainly beyond the intended responsibility of `RRCollator`
 > (which is expected to be reasonably stateless - for complete collation
 > we need to expect to have a temporary storage for the entire zone in
 > the worst case).  So, it should be done in `RRsetCollection`.  I guess
 > we need to be able to "merge" an (newly given) RRset into another
 > (already stored in the collection).  Note also that if we implement it
 > by modifying the stored RRset, it means the result of a previous call
 > to find() can be changed.  This should be documented.
 >
 > Anyway, in completing #2433 I realized I didn't need full collation
 > for it, and we won't need it for the rest of the zone validation/check
 > tasks.  So I suggest deferring this part to a separate task.

 In this case, I'll open a new ticket (before resolving this ticket after
 merge to master when such a ticket would be applicable).

 Passing it back to Michal for regular review.

-- 
Ticket URL: <https://bind10.isc.org/ticket/2432#comment:30>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list