From: Logan Capaldo <logancapaldo@...>
Date: 2006-05-23T09:08:53+09:00
Subject: Re: Embedding ruby in aolserver (Was: Re: segfault when calling rb_eval_string_protect ...)


On May 22, 2006, at 3:57 AM, Mark Aufflick wrote:

> Hmm I see. That could be a bit of a problem for my application given
> that aolserver is highly threaded. I'd have to make a pool of
> interpreters and supervise access to them to ensure only one thread is
> using each interpreter at once...
>

Making a pool of interpreters could have it's own problems. AFAIK,  
Ruby doesn't support multiple interpreters in the same process.

> I'm also starting to look at the work going into the byte compilers -
> if I could have a pool of compilers, cache the bytecode and then only
> fire up a vm for each request that might be ok.
>
> Any timeline for thread safety?
>
> On 5/22/06, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
>> README.EXT in the distribution and the Pickaxe book.  Note that Ruby
>> interpreter is not thread safe at all (yet).  Only one thread can
>> access Ruby interpreter at a time.
>>
>>                                                         matz.
>