Hey Maxime,
My thoughts on possible improvements for mod_wombat are as follows:
* Lua bindings for relevant portions of the Apache Portable Runtime;
the io, lfs (LuaFileSystem) and luasocket libraries look like they
could be nicely done through APR functions
* Better win32/VisualC++ support
* Comp
One new bit of apr "glue" to complement apr_table.get and
apr_table.set : apr_table.foreach
Index: apr_lua.c
===
--- apr_lua.c (revision 653202)
+++ apr_lua.c (working copy)
@@ -46,9 +46,30 @@
return 1;
}
+static APR_DECLAR
I didn't have trouble building it on linux, however:
1) I cannot build it on windows; the first part of the win32 build
instructions is "perl Makefile.pl" from the libapreq folder, which for
me throws up lots of dialog boxes saying expr.exe, sed.exe, chmod.exe,
rm.exe, sh.exe, bash.exe and/or basen
as this occurs under some configurations but we haven't
hammered down the weird things libapreq2 does with its
install. If you build libapreq2 with a --prefix configuration
option, it always seems to work.
2008/5/21 Matthew M. Burke <[EMAIL PROTECTED]>:
> Corsix wrote:
>
Hi,
While using mod_wombat and attempting to use luasocket (with require
"socket"), I get a white screen. Assuming test.lua is:
-- code --
function handle(r)
r:write "Start\n"
require "socket"
r:write "Done\n"
end
-- end code --
The expected output when requesting this page via a web browser
Seems I was wrong; commenting out that call doesn't make luasocket
load. This still leaves the main question unresolved though; why does
require"socket" cause a blank response (as even a standard error would
be caught by mod_wombat's usage of lua_pcall)?
2008/8/8 Corsix <[
