Hi, list! I'm trying WSAPI (in the nginx+spawn_fcgi+wsapi.fcgi flavor on Ubuntu Linux) to do some quick prototyping, and have stumbled upon some inconveniences.
It is quite possible that it's just I'm doing something wrong. If it is so, please point me in the right direction. 1. WSAPI does not react to changes in files unless restarted. I want some kind of reload command. 2. If I run io.popen() and do not close the file explicitly, I have a zombie process hanging around (my wild guess is that it happens because GC does not kick in, as my script does not create enough garbage). 3. I can't supply a callback to WSAPI without wrapping it in a Lua module. I'd like to avoid this. 4. WSAPI pollutes global environment (with main_func and main_coro symbols). I'd like to avoid adding exceptions to my pet strict module. 5. WSAPI handles duplicate request keys by putting all their values into a table. I need to get more PHP-like behavior, when next value for the duplicate key would override previous one. I had to copy and change the request module to get this behavior. I do want a configuration option. None of these issues are critical (I'm planning to write my own specialized Lua-FCGI binding for the production anyway), but I wanted to share them just in case. :-) Alexander. _______________________________________________ Kepler-Project mailing list Kepler-Project@lists.luaforge.net http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project http://www.keplerproject.org/
