From: Charles Oliver Nutter <charles.nutter@...>
Date: 2008-07-30T16:10:19+09:00
Subject: Re: Concurrent Ruby?

David Masover wrote:
> On Tuesday 29 July 2008 11:56:43 Charles Oliver Nutter wrote:
>> They  
>> do require a bit more diligence on your part if you're sharing data 
>> across the threads,
> 
> That's the whole problem that I'm attacking right now -- while a pure actor 
> model wouldn't share any data, I'm not even sure I can safely clone 
> everything properly, if I was going that route. And I'd rather not, for 
> obvious performance reasons.

Well if there are specific threading issues, we'd like to solve them. 
And at this very moment we're debating and working on ways to make the 
core collection types (String, Array, Hash) at least not dump a stack 
trace when they're used unsafely. So I think there's little reason why 
you couldn't implement a decent Actor framework on top of JRuby.

Also, we recently added Rubinius's MVM API atop our existing MVM 
support, so that's another route you can go and really isolate 
instances. But of course, they eat up more memory that way.

- Charlie