On Wed, Apr 13, 2011 at 16:45, Robert G. Jakabosky <[email protected]> wrote: > On Wednesday 13, Alexander Gladysh wrote: >> On Wed, Apr 13, 2011 at 14:32, Fabio Mascarenhas <[email protected]> > wrote:
>> > 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). >> Um. Did you just suggest to reuse the same state from two threads? > You wouldn't be able to share the same lua_State between two threads with my > lua-llthreads module. The same is true for Lanes. And I should not be able to. It is a bad idea. Alexander. _______________________________________________ Kepler-Project mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project http://www.keplerproject.org/
