Opened 9 years ago

Closed 6 years ago

#1015 closed task (wontfix)

unify configuration/command code for auth and resolver

Reported by: jinmei Owned by:
Priority: medium Milestone: DNS Outstanding Tasks
Component: resolver Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 6.0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


Looking at the (b10) resolver configuration code, I start feeling
we should unify the server configuration code for both b10-auth and
b10-resolver (and, probably the DHCP servers eventually).

The current implementation for b10-resolver is a big single method
that is responsible for everything: parsing config parameters,
building internal configuration data from the passed param, and doing
this for all parameters in the single function. Clearly this approach
won't scale as we add more parameters.

My suggestion is to use the auth/auth_config.{h,cc} and
auth/command.{h,cc} by moving them to lib/server_common (and rename
them appropriately), adjusting them if necessary so that they can work
with the resolver, and have the resolver use it.

We should perhaps also consider making the hardcoded factory logic
in more generic using this


Change History (3)

comment:1 Changed 9 years ago by stephen

  • Estimated Difficulty changed from 0.0 to 6

comment:2 Changed 6 years ago by stephen

  • Milestone set to DNS Outstanding Tasks

comment:3 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed

DNS and BIND10 framework is outside of scope for Kea project.
The corresponding code has been removed from Kea git repository.
If you want to follow up on DNS or former BIND10 issues, see project.

Closing ticket.

Note: See TracTickets for help on using tickets.