[Oisf-wg-configuration_language] Working group summary.

[Jason Ish]

Hello everyone.

August 12 has come and gone so here is a summary of how we'll proceed based
on the input of the working group.

The configuration file will be YAML.  YAML provides a good middle ground
between hand-editing and machine parsing/editing vs yet another custom
format or more verbose machine readable formats like XML.  It should also
make it easier to bolt-on management applications on top of the engine vs a
custom format due to the number of YAML libraries out there for an
assortment of languages.  And while white space does mean something, its a
little more lenient than Python when it comes to what the space actually is.

On the code side the internal configuration format will not be tightly
coupled with the YAML format.  The engine will also allow for configuration
parameters that are not known to the engine to be specified and made
accessible via the configuration API.  The configuration API will also be
along the lines of a suggested API like: cfg_get_bool("section.name",
&my_bool, default_value, required).

We hope this is satisfactory for everyone involved.

Thanks for the input.
Jason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openinfosecfoundation.org/pipermail/oisf-wg-configuration_language/attachments/20090817/509ef123/attachment-0002.html>