[Kea-users] Need help defining custom options

[Francis Dupont]

 As Vicky said in another response the ticket is under review so it will
be merged before the 1.2 release but the delay from today is only bounded
(I have no control on it as I wrote the patch so I may not review it too).
 I pushed the trac5105 branch on github so you can take it. There is only
one commit so it is easy to make a patch from it and to apply it to
Kea 1.1 sources. I am checking it: patch succeeded with different offsets
(not a problem: this just means some files have changed since 1.1).
I am running a full check and I expect it will be successful.
 An important detail: to not be misinterpreted as a field separator
commas must be escaped. The escape character is the backslash \ which
is also the escape one for JSON and C++ so to put foo,bar into an
option data string value you have to use "data": "foo\\,bar"
(and in C++ examples this becomes \"data\": \"foo\\\\,bar\" in
the case you read the patch content).
 BTW something I expect from the reviewer is a request for documentation
so if you have an idea about to explain the escape feature in the Kea
user guide...

Regards

Francis Dupont <fdupont at isc.org>

PS: to clone the github repository:
 git clone https://github.com/isc-projects/kea.git

if you already have a clone, don't forget to pull it and to checkout master.
To get the patch:
 git diff ...origin/trac5105 > trac5105.diff

To apply the patch go to your kea sources and:
 patch -p1 < trac5105.diff

And build kea...