On Jan 15, 2014, at 10:21 AM, Yongming Zhao <ming....@gmail.com> wrote:
> looks great, that rise me an very important issue, we have a heavy modified > remap system, that is a blocking for me to keep in sync with apache tree, can > I expect we can make the remap module a easy to extent system which we can > put origin remap.config, the new lua config, our ugly remap config, or even > someone may write squid style & varnish style config? > > please consider my concerns, and help me out. thanks Yeah, you could for example write a Lua script that reads your format :). I’d imagine once things are done, we’ll have Lua scripts that reads all the old configurations as well, as a migration path. Note that we’re still in very early state of this, so everyone work on the specifications, reviews and code :), but as a proof of concept, I believe Theo already wrote a simple parser that read LI’s YAML format! This is the power of a scripting format, and why we picked Lua, it makes it really easy to do these things. We just have to make the bindings easy to use and flexible. Another thing that was discussed was to replace the guts of all configs inside the core, and use TSConfig as an intermediary layer. I don’t know if Alan has pondered over this any more, or if it’s still reasonable. One concern of course is that various configurations (e.g. remap.config vs records.config) have vastly different requirements on the underlying data structures. This is orthogonal from the Lua fronted (IMO), and I see it mostly as a way to simplify and cleanup our config guts (but alas, it’s possible we could expose TSConfig format to the users as well). Cheers, — Leif
