>> I was under the impression that it was positioned as a Lua-flavored >> replacement for the traditional CGI programming API. Of course I may be >> completely wrong. I am curious to hear what Fabio has to say on the subject.
<...> > In practice it is a very thin wrapper over the interface that CGI and > FastCGI provides: an environment with http headers in the form HTTP_*, plus > several agreed-up variables such as SCRIPT_NAME, PATH_INFO, REQUEST_METHOD, > QUERY_STRING, etc., plus pipes for reading postdata and writing back the > response (with status and headers as separate entities). CGI/FastCGI is kind > of the common denominator among server interfaces, with Apache's mod_* and > IIS's ISAPI being easily converted to it. > The idea is to code your application/framework against WSAPI and have it run > mostly unmodified under CGI/FastCGI/Xavante/anything else with an WSAPI > adapter. The interface is also well-suited to writing filters (WSAPI > applications that wrap another WSAPI application). <...> Thanks for a detailed description! Some things in my head just got clearer. > Stefan, a great thing that luafcgid can do is "process"-management, with > watchdogs, restarting of processes that go AWOL, etc., things that > wsapi-fcgi currently delegates to an external tool (mod_fcgid, lighttpd, > spawn-fcgi+a process monitor, etc.). A rock-solid FastCGI daemon for Lua > scripts would be very useful. You might get some ideas from the Ruby folks > and their Unicorn web server (Unicorn speaks HTTP instead of FastCGI, but > the general idea is applicable, IMHO). I'm looking closely at the Unicorn as well. This article is insightful: http://tomayko.com/writings/unicorn-is-unix Unicorn looks like is a good model for a Lua web-server. Alexander. _______________________________________________ Kepler-Project mailing list Kepler-Project@lists.luaforge.net http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project http://www.keplerproject.org/
