On Thu, Dec 9, 2010 at 1:41 PM, McClure, Timothy J UTCFS <tim.mccl...@fs.utc.com> wrote: > Thanks very much for your help. I am excited to start digging into CGILua > and feel it will satisfy our needs. I have a couple of quick questions: > > I made a patch to common.lua for WSAPI to get it to work with mini-httpd. > Will this patch be incorporated into the product?
Yes, as soon as I get a mini-httpd test environment up. Won't have time for that until next week, though... > Running with the patch I noticed that test.lp still displayed the > SCRIPT_NAME variable as blank, will this be a problem? In your patched > version will it still be blank? This is the underlying cause, mini-httpd is not following the CGI 1.1 RFC correctly... is DOCUMENT_ROOT coming up fine, at least? This will make it easier to have a workaround and set a good SCRIPT_NAME myself. > I am using cgilua.cgi is my scripts moving forward. I think this technology > still leverages WSAPI - am I correct? Yes, it is all WSAPI underneath. > Is all the functionality listed of this website > http://www.tecgraf.puc-rio.br/~tomas/htk/ available through cgilua? > Through Google I saw that people are using cgilua on an embedded arm > processor running Linux. This is our target environment. Do you see any > issues with this environment? Not at all. Also, if you are going to be using mini-httpd mostly to serve Lua pages instead of static content, you might also want to consider going 100% Lua and using Xavante directly. -- Fabio Mascarenhas _______________________________________________ Kepler-Project mailing list Kepler-Project@lists.luaforge.net http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project http://www.keplerproject.org/
