||08-02-2013 02:50 AM
Originally Posted by ponce
it's still considered experimental by the apache developers theirselves...
Just a note from one of the core developers on this module; By "experimental" we do not mean "it doesn't work and is unsupported", what we mean is; It's still being worked on actively, and new features may enter into play at any given time. Some internal mechanisms may get upgraded, some default directive values may change, but your scripts/usage would stay largely unaffected by this. If you write a script do to X, then you can rest assured that it'll still do X in the next version of httpd, there just may be another way of doing X, or it may be recommended/preferred to do Y instead at that point. I've used mod_lua since the birth of httpd 2.4, and I haven't had to change or invalidate my scripts since that time, I've ever only had the pleasure of upgrading scripts to take advantage of new features as they became available (the database interface for example). On a few occasions, I've had to change minor bits and bobs in my code, but that has usually been because we found a more clever way of writing a function (for instance, changing a return value from an int to a float, or accepting more arguments in a regex function).
To put this into perspective; We at Apache use mod_lua for quite a bit of sites, including (but not limited to) our modules database, our paste bin, our online commenting system and so on. All these sites are freely available under the ALv2 license in our subversion repositories, and we're quite comfortable using this on production servers.
To sum up; We quite like (working with/on) this module, it's just as safe to use on production servers as any other language module, we're actively working on enhancing it, and we'd love to answer any questions (whether it be tech support or just how to use it) on either IRC (#httpd on Freenode) or on one of our mailing lists.