-
Notifications
You must be signed in to change notification settings - Fork 974
auth: Überbackend code cleanup #16542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Pull Request Test Coverage Report for Build 19757600681Details
💛 - Coveralls |
the only thing using it appears to be a |
Habbie
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice cleanup
pdns/ueberbackend.cc
Outdated
| { | ||
| DLOG(g_log << "Ueber get() was called for a " << qtype << " record" << endl); | ||
| bool isMore = false; | ||
| while (d_hinterBackend != nullptr && !(isMore = d_hinterBackend->get(record))) { // this backend out of answers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
late note: this comment is missing a word
This allows making the current backend pointer private and makes the behaviour more explicit: - all backends will be queried in sequence. - as soon as one backend answers the given (qname, qtype) query, none of the remaining backends will be queried until the next UeberBackend::lookup call (which starts a fresh new query). Signed-off-by: Miod Vallat <[email protected]>
Signed-off-by: Miod Vallat <[email protected]>
Signed-off-by: Miod Vallat <[email protected]>
3e81f60 to
a212ab4
Compare
Signed-off-by: Miod Vallat <[email protected]>
Short description
This apparently simple PR reworks the behaviour of the
handleinternal object ofUeberBackendto:lookupcall.It is not supposed to introduce any behaviour change. But it will help make further (possibly breaking) changes in
UeberBackendwith confidence.P.S.: do we really need to keep the
instancesatomic counter? It doesn't seem to be used by anything and its value is not retrievable either.Checklist
I have: