[
https://issues.apache.org/jira/browse/TS-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398840#comment-15398840
]
Kit Chan commented on TS-4548:
------------------------------
Some quick notes. I think I can imply how the rest looks like. A few
suggestions
1) Should we have an array of log objects for the "log" variable? I think we
can have multiple log objects. e.g.
{code}
log = {}
log[1] = {...}
log[2] = {...}
{code}
2) We probably need some predefined variables to use in the config file. e.g.
mode can be "ASCII", "BINARY", "ASCII_PIPE" and match operator for filter can
be "MATCH", "CONTAIN", etc.
3) perhaps this is better?
{code}
wipe_pass = filter.wipe("cquc", CONTAIN, "passwd")
{code}
> Convert custom log config file to Lua
> -------------------------------------
>
> Key: TS-4548
> URL: https://issues.apache.org/jira/browse/TS-4548
> Project: Traffic Server
> Issue Type: Improvement
> Components: Logging, Lua
> Reporter: James Peach
> Assignee: James Peach
> Fix For: 7.0.0
>
>
> Custom logs {{logs_xml.config}} is a good candidate to convert to Lua
> bindings. I'm thinking that we bind fairly directly to the internal logging
> objects so that conceptually it is the same but instead of using XML to
> construct objects, you use Lua. We would just construct Lua states on the fly
> to evaluate the file.
> This is the last usage of XML and would let us nuke {{proxy/shared/InkXml.*}}
> as well as our dependencies on expat+libxml2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
