You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2016/06/03 22:19:59 UTC

[jira] [Updated] (TS-4505) Generic config file parsing that works

     [ https://issues.apache.org/jira/browse/TS-4505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-4505:
------------------------------
    Fix Version/s: sometime

> Generic config file parsing that works
> --------------------------------------
>
>                 Key: TS-4505
>                 URL: https://issues.apache.org/jira/browse/TS-4505
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Cleanup, Core, Management API
>            Reporter: James Peach
>             Fix For: sometime
>
>
> We have a big mess in config file parsing.
> The management API uses {{./mgmt/api/GenericParser.*}} to parse mostly generic key=value syntax, but nothing calls those APIs. We should remove them.
> Internally, other files are parsed by hand (each with a different set of bugs) or by using {{parseConfigLine}}, which was not really intended for generic parsing and has a kind of crappy interface.
> What we need is to nuke all this code and have a single interface for parsing files sanely. The top level parser maps a file and emits a stream of lines. This should support comments, empty line elision and line continuations. Each line should come with a {{SourceLocation}} object for error messages. The stream of lines is consumed by a key=value tokenizer that each subsystem digests. This would be broadly similar to the {{GenericParser}} stuff.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)