From: Logan Capaldo Date: 2006-05-25T03:21:12+09:00 Subject: Re: Embedding ruby in aolserver (Was: Re: segfault when calling rb_eval_string_protect ...) On May 24, 2006, at 3:24 AM, Tim Becker wrote: > 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 5/23/06, Mark Aufflick wrote: >> Yes, they would have to be in seperate processes, which then loses >> the >> benefits of aolservers fantastic inter-thread communication. >> >> Maybe I should just help out with one of the VM projects and make >> sure >> that they are thread safe. The interpreter at least - the compiler >> being thread safe is not as important. >> >> On 5/23/06, Logan Capaldo wrote: >> > Making a pool of interpreters could have it's own problems. AFAIK, >> > Ruby doesn't support multiple interpreters in the same process. >> >> > 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.