Timothy Goddard wrote:
If the library is completely separated from ruby iself and its only
interface with the ruby interpreter is through a single thread, I
don't think you should have problems. You just don't want any part of
the ruby interpreter running in two threads of the same process at
once. I could be wrong, but I'd just give it a test. The worst you
can do is crash it.
+1 - Completely agree to all your points.
robert