[Note: parts of this message were removed to make it a legal post.]
On Sat, Apr 25, 2009 at 5:45 PM, jamesl <ladd.ja...@gmail.com> wrote: > I'm wondering if anyone would like to see a Concurrent Library for > Ruby, like the Java javax.concurrent library ?
There are quite a few libraries that provide concurrency strategies already
On Apr 26, 10:52 am, Tony Arcieri <t...@medioh.com> wrote:
> [Note: parts of this message were removed to make it a legal post.]
> On Sat, Apr 25, 2009 at 5:45 PM, jamesl <ladd.ja...@gmail.com> wrote: > > I'm wondering if anyone would like to see a Concurrent Library for > > Ruby, like the Java javax.concurrent library ?
> There are quite a few libraries that provide concurrency strategies already
[Note: parts of this message were removed to make it a legal post.]
On Sat, Apr 25, 2009 at 7:10 PM, jamesl <ladd.ja...@gmail.com> wrote: > Like ? Do you have a few URL's to share?
Well, I'm not sure what you're after. Two libraries for actor-based concurrency (one of them mine) have been linked, but those aren't really anything like java.util.concurrent.
Are you wanting a small framework for backgrounding work into "thread" pools? (which would more likely be implemented as process pools)
Ruby's threads provide only sequential execution, since Ruby's memory model is inherently sequential. For concurrent processing it's best to farm things off to additional processes so that the OS's scheduler can make them concurrent. There are packages to do this as well (e.g. BackgroundDRb)
[Note: parts of this message were removed to make it a legal post.]
If you are looking for a process pool or similar, http://abundance.rubyforge.org/ it forks an n amount of concurrent process workers then seed/harvest them by unix sockets communication,
> On Sat, Apr 25, 2009 at 7:10 PM, jamesl <ladd.ja...@gmail.com> wrote:
> > Like ? Do you have a few URL's to share?
> Well, I'm not sure what you're after. Two libraries for actor-based > concurrency (one of them mine) have been linked, but those aren't really > anything like java.util.concurrent.
> Are you wanting a small framework for backgrounding work into "thread" > pools? (which would more likely be implemented as process pools)
> Ruby's threads provide only sequential execution, since Ruby's memory model > is inherently sequential. For concurrent processing it's best to farm > things off to additional processes so that the OS's scheduler can make them > concurrent. There are packages to do this as well (e.g. BackgroundDRb)
