Re: Low-Level Concurrency library

["D. Matt Placek" <atomicsuntan@...>]

On Tue, Jan 14, 2014 at 10:03 AM, Andrew Starks <andrew.starks@trms.com> wrote:

Lanes is awesome work. However, this is an example of something that is at a higher level than what I was thinking. For example (and as far as I could tell from looking at Lanes), it uses its own message passing functions. We have a desire to stick with nanomsg (or similar), in order to achieve network transparency. This will lead to other issues (endianness, byte alignment), of course.

I'll take another look at Lanes, however. It is an interesting project.

The complexity of sharing values between states is why I prefer a concurrency strategy that primarily uses coroutines.  Where I have blocking I/O I will use a separate thread and use lanes/lindas to transfer the data in as raw a form as practical to/from a coroutine in my primary lua state.  By moving all blocking operations to separate threads/lanes, the coroutines in the main state are always responsive and low latency.  Keeps things much simpler.  Of course, that doesn't help with network transparency or if you really need multiple threads to take advantage of multiprocessor bandwidth.