Actor concurrency model for Rubinius. We can't seem to get message passing working right, so we're throwing a Mutex into the mix for now. Hopefully somebody can fix things for us. Currently, this is exactly the same as the ThreadSpawn model since we don't use the message passing capabilities of the Actor model (and even then it wouldn't really make sense since Actors in Rubinius are just Threads underneath and our ThreadSpawn model is one layer of complexity less.
This is different from the Revactor one which is not prone to race conditions within the same process at all (since it uses Fibers).
Included modules: Rainbows::ThreadSpawn
Pages Classes Methods
mail archives: https://bogomips.org/rainbows-public/ nntp://news.public-inbox.org/inbox.comp.lang.ruby.rainbows nntp://news.gmane.org/gmane.comp.lang.ruby.rainbows.general public: email@example.com / private: firstname.lastname@example.org