Does someone on this list have experience with running Lua in a threaded environment?
I am thinking about the following scenario:
- A main thread creates a Lua state and uses it the usual way using the C API.
- A secondary thread should call a function in said Lua state from time to time,
asynchronously and not predictable when it will do so. Totally independent from
the main thread.
It's obvious that this will not work and that some sort of arbitration will be needed. As
I understand, there is no locking at all in Lua, and not even a function to query if a
Lua state is currently executing Lua code, i.e. if another thread is running the Lua
interpreter.
What's the best approach to this? I think I will have to add a locking mechanism
and aquire the lock before calling any of the Lua C API functions. Are there better
ways?
Already a while ago I specifically wrote a library [1] that can be used to signal incoming data from a background thread using sockets. I used it for a UPnP background process/thread and on a raspberry pi, to signal events from the GPIO interface
[2] (also from a background thread).
generally combined with the Copas scheduler [3]
Thijs
|
