BIND 10 #2490: Option definitions: multiple data formats to be accepted to create option instance.

[BIND 10 Development]

#2490: Option definitions: multiple data formats to be accepted to create option
instance.
-------------------------------------+-------------------------------------
            Reporter:  marcin        |                        Owner:
                Type:  task          |                       Status:  new
            Priority:  medium        |                    Milestone:
           Component:  dhcp          |  Sprint-DHCP-20121129
           Sensitive:  0             |                     Keywords:
         Sub-Project:  DHCP          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 Currently the OptionDefinition object returns the instance of the factory
 function that can be used to create option. This factory function takes
 OptionBuffer as an argument. We need other !''data formats!'' to be
 accepted too:
 - Comma separated values: to allow user put values for particular option
 values separated with comma sign which is more convenient when defining
 option values in the config manager.
 - iterators: when packet is received from the client it is stored in the
 buffer that comprises many options. It is required to supply chunk of this
 buffer, which represents the particular option, to an OptionDefinition
 object. This chunk of buffer is specified with two iterators (specifying
 begin and end of the chunk).

-- 
Ticket URL: <http://bind10.isc.org/ticket/2490>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development