BIND 10 #2545: Option value to be specified in in CSV format in Config Parser
BIND 10 Development
do-not-reply at isc.org
Fri Dec 21 13:10:13 UTC 2012
#2545: Option value to be specified in in CSV format in Config Parser
-------------------------------------+-------------------------------------
Reporter: marcin | Owner:
Type: task | UnAssigned
Priority: medium | Status:
Component: dhcpconf | assigned
Keywords: | Milestone:
Sensitive: 0 | Sprint-DHCP-20130103
Sub-Project: DHCP | Resolution:
Estimated Difficulty: 0 | CVSS Scoring:
Total Hours: 0 | Defect Severity: N/A
| Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by marcin):
* owner: marcin => UnAssigned
* status: accepted => assigned
Comment:
The ticket is now ready for review. The new configuration parameter has
been added to the spec file. This parameter accept boolean value that
controls whether option data is entered as a string of comma separated
values (where each value initializes one option field) or as a string of
hexadecimal digits that represent the binary content of a whole option.
I also made a couple of changes to the existing configuration parsers:
- more clear separation of the build() phase from the commit() phase - the
latter should simply apply parsed values to the server's configuration and
should be exception safe as much as possible
- moved the parser classes to an anonymous namespace as they are not
intended to be accessed externally
Changes applied to v4 '''and''' V6 parsers.
Please review.
--
Ticket URL: <http://bind10.isc.org/ticket/2545#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list