On Wed, Apr 13, 2011 at 3:32 AM, Alexander Gladysh <aglad...@gmail.com> wrote: > Here is a link to yet another my ignored post from a year ago, that > somewhat explains the problem with signals: > > http://lists.luaforge.net/pipermail/kepler-project/2010-April/004158.html > > Maybe I just should try again?
In an ideal world all Lua I/O would be handled by the same scheduler, so you could block on a read from the FCGI pipe and still receive signals, or other events. But you can still use one of the thread libraries (Lanes, or the one that Robert of this thread just released, I am sure there are others) to spawn a thread that just waits and responds on signals (lather, rinse, repeat for other kinds of events that cannot wait). Maybe the community will converge on the proper way to handle I/O and events someday, then we can all rewrite our modules to support it. :-) Even Mike has taken a stab at this several years ago: http://lua-users.org/lists/lua-l/2004-06/msg00586.html http://lua-users.org/files/wiki_insecure/users/MikePall/event.html Perhaps he decided this was too hopeless a task, and that building a JIT would be way easier. :-) > Alexander. > > -- 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/
