From: Tim Becker <a2800276@...>
Date: 2006-05-24T16:24:35+09:00
Subject: Embedding ruby in aolserver (Was: Re: segfault when calling rb_eval_string_protect ...)

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 <mark-ruby@aufflick.com> 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 <logancapaldo@gmail.com> wrote:
> > Making a pool of interpreters could have it's own problems. AFAIK,
> > Ruby doesn't support multiple interpreters in the same process.
>
>