BIND 10 #2435: implement datasrc version of RRsetCollection
BIND 10 Development
do-not-reply at isc.org
Wed Jan 9 22:52:38 UTC 2013
#2435: implement datasrc version of RRsetCollection
-------------------------------------+-------------------------------------
Reporter: jinmei | Owner: muks
Type: task | Status:
Priority: medium | reviewing
Component: data source | Milestone:
Keywords: | Sprint-20130122
Sensitive: 0 | Resolution:
Sub-Project: DNS | CVSS Scoring:
Estimated Difficulty: 4 | Defect Severity: N/A
Total Hours: 0 | Feature Depending on Ticket:
| loadzone-ng
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Comment (by jinmei):
If you choose to define `RRsetCollection` to be created from updater,
it looks just confusing to have a separate definition for
`datasrc::RRsetCollection`. What we should do (or at least what I
envisioned) is to think about pros and cons of both approaches, pick
one and only one of them and implement it.
Also, if the decision is to extend the updater, we should generally
need more doc than this:
{{{#!cpp
/// Return an RRsetCollection for the updater.
virtual isc::dns::RRsetCollectionPtr getRRsetCollection() = 0;
}}}
(unless it's already planned). Sometimes a one-liner brief doc is the
best we can have, but that should be very rare except for trivial
getter/setter.
--
Ticket URL: <http://bind10.isc.org/ticket/2435#comment:10>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list