Someone may want to add some text along the lines of when to use u/WSGI instead of mod_lua as that's going to be a thing if this goes stable. If the what/when isn't in there clearly we could run into really bad situations like ASF using mod_lua to host web services in production.
On Fri, Jan 25, 2019 at 2:36 PM Eric Covener <cove...@gmail.com> wrote: > On Fri, Jan 25, 2019 at 2:12 PM Frank Kuhn <fr...@x09.de> wrote: > > > > > > > > On 12/17/18 8:23 PM, Daniel Gruno wrote: > > > Hi folks, > > > I've been pondering on the state of mod_lua, and it seems like it's > time > > > to get rid of the 'experimental' note, which still scares off a lot of > > > people. The API has been steady over the past few years, I believe, and > > > the code itself seems to be in a stable state, so I'm inclined to go > > > ahead and get it moved over to stable, including switching from CTR to > RTC. > > > [...] > > > > Hi, > > I have big problems with LuaOutputFilter and SetOutputFilter (see > > https://bz.apache.org/bugzilla/show_bug.cgi?id=62726) so I cannot call > > it 'stable'... > > Stable from an API perspective, not bug-free. The disclaimer we have > used recently for experimental is: > > > This module is experimental. Its behaviors, directives, and defaults are > subject to more change from release to release relative to other standard > modules. Users are encouraged to consult the "CHANGES" file for potential > updates. >