Opened 9 years ago

Closed 6 years ago

#808 closed task (wontfix)

Research alternate strategy of using a lexer/parser to define record types

Reported by: stephen Owned by:
Priority: low Milestone: Remaining BIND10 tickets
Component: Unclassified Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity:
Sub-Project: Feature Depending on Ticket:
Estimated Difficulty: 8.0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

Rather than explicitly creating a class for each record type, is there some way that we can define the characteristics of a RR and automatically generate the code?

Subtickets

Change History (2)

comment:1 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:2 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to old-bind10

This issue is related to bind10 code that is no longer part of Kea.

If you are interested in BIND10/Bundy framework or its DNS components,
please check http://bundy-dns.de.

Closing ticket.

Note: See TracTickets for help on using tickets.