Just because aolserver is multithreaded doesn’t mean that you need to
access the ruby interpreter from each thread. Just make sure that only
one thread accesses the interpreter at a time or create a single
thread that access is funneled through.
-tim
On May 24, 2006, at 3:24 AM, Tim B. wrote:
I think part of the reason he wanted to do this (after all there’s
already mod_ruby, mongrel and fastcgi) is precisely because of
aolserver’s thread-heavy architecture. Using only one interpreter
kinda kills the point.