Re: Re[2]: Question about multi-threading in Lua

[askok@...]

Lua Lanes is ready for usage; the "beta" is simply because 
I feel it hasn't been tested in field enough.

Maybe it has, and I just haven't received much feedback on 
it (to users: just saying "it works" is valuable 
information to the authors :)

I intend to package it as a Lua Rocks within the next 
month or so.

-asko

[ Anyone wishing to take on PR management of my projects 
would be appreciated; I seem to stop when it works for me, 
and I've pushed the code to luaForge. ]



On Fri, 16 May 2008 03:02:18 -0700 (PDT)
 gary ng <garyng2000@yahoo.com> wrote:
> Thanks for the info. I actually mixed up LuaTask with
> LuaThread. Was meant to say LuaTask which as far as I
> know has seperate lua_state for each thread, I believe
> the design is very similar to LuaLane.
>
> I just don't know what is the state of LuaLane, it
> said beta since May 2007.
>
> --- Alexey Malyshev <malma@kaluga.net> wrote:
> > Yes, LuaThread is easier to code, but I recommend
> > you to use
> > LuaLanes. LuaThread depends on lock\unlock mechanism
> > in lua core,
> > which is very uneffective in real multithreading.
> > Lanes runs
> > independend threads with asynchronous
> > communications.
> > --
>
>
>
>