RE: [ANN] DarkSideSync, general async callback support

["Thijs Schreijer" <thijs@...>]

> -----Original Message-----
> From: lua-l-bounces@lists.lua.org [mailto:lua-l-bounces@lists.lua.org]
> On Behalf Of Javier Guerra Giraldez
> Sent: dinsdag 25 september 2012 19:12
> To: Lua mailing list
> Subject: Re: [ANN] DarkSideSync, general async callback support
> 
> On Tue, Sep 25, 2012 at 7:28 AM, Thijs Schreijer
> <thijs@thijsschreijer.nl> wrote:
> > DarkSideSync (DSS) is a library with no use on its own, it only
> > supports other (multi threaded) libraries in handling async
> callbacks.
> > It’s loaded by/from Lua and supports many libraries simultaneously,
> as
> > long as they are designed to work with DSS. For now it only supports
> > Windows (have to do the socket/lock wrapper code for unix still).
> 
> have you seen my Helper Threads Toolkit [1] ?
> 
> does roughly the same things (for POSIX systems), while presenting a
> simple C API for for adapting libraries (just add a function for
> preparation, work, and delivery) and a regular Lua API (including a
> simple optional coroutine scheduler)
> 
> 

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.

And on top of that, I need Windows support.