an implant fires up a new thread per conjoiner connection. Ruby's green threads are not really running in parallel (JRuby and some other implementations avoid GIL): http://merbist.com/2011/10/03/about-concurrency-and-the-gil/, which is ok in this case (and is similar to the other implementations).
But eventually we should have a look at EventMachine or similar. Doing some measurements, we can find out if they would perform better in a topology of several conjoiners writing to same values while keeping values changed by transenlightenments safe against parallel destructive writes. Not really an issue, just something to keep in mind and to test.
an implant fires up a new thread per conjoiner connection. Ruby's green threads are not really running in parallel (JRuby and some other implementations avoid GIL): http://merbist.com/2011/10/03/about-concurrency-and-the-gil/, which is ok in this case (and is similar to the other implementations).
But eventually we should have a look at EventMachine or similar. Doing some measurements, we can find out if they would perform better in a topology of several conjoiners writing to same values while keeping values changed by transenlightenments safe against parallel destructive writes. Not really an issue, just something to keep in mind and to test.