lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]


On Tue, Sep 25, 2012 at 12:58 PM, Thijs Schreijer
<thijs@thijsschreijer.nl> wrote:
> Different usecase, HTT spawns a new process and returns it results. In my case (the pupnp library and the openzwave library) the libraries just get started, and then run in the background, whenever something happens, they run callbacks on (at least from the client library perspective) unknown threads. So I have no control over the background threads coming in.
> I think QT is another such library that occasionally returns a callback on another thread and wreaks havoc in the Lua state.


I see.   HTT design is more to make it easy to send blocking libraries
off to helper threads.  It can be used when the library already
handles concurrency, but i guess it could be simpler in that case.

as for windows, it was reported to work with a pthread emulation
library; but that's precisely what you don't need from HTT.

cheers,

-- 
Javier