BIND 10 #2432: define and implement base and libdns++ version of RRsetCollection
BIND 10 Development
do-not-reply at isc.org
Fri Nov 2 16:57:10 UTC 2012
#2432: define and implement base and libdns++ version of RRsetCollection
-------------------------------------+-------------------------------------
Reporter: | Owner: UnAssigned
jinmei | Status: new
Type: task | Milestone: New Tasks
Priority: | Resolution:
medium | Sensitive: 0
Component: | Sub-Project: DNS
libdns++ | Estimated Difficulty: 0
Keywords: | Total Hours: 0
Defect Severity: N/A |
Feature Depending on Ticket: |
loadzone-ng |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:1 vorner]:
> Looking at the definition, would it be better to have some kind real
iterator
> than a foreach method with callback? I find the loop-by-callback
> counter-intuitive.
I don't know. This reminds me of a discussion we had for the
`RdataReader` class, and my sense is that this is a matter of
preference. I don't necessarily object to making it an iterator,
but I don't necessarily think it's clearly a better choice either.
If we could make it an STL-compatible iterator, I'd probably agree
it's better, because the interface should be much more familiar for
others and it can benefit from STL algorithms, etc. Unfortunately, in
this case this has to be a virtual interface, so this option is not
easy (if not impossible).
One possible idea I just come up with is:
- introduce an STL-compatible iterator interface in the base class
(this is not virtual). this will be a forward iterator.
- introduce some way that can work as a backend of the top level
iterator in each class, maybe via protected methods
--
Ticket URL: <http://bind10.isc.org/ticket/2432#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list