From: "Hal E. Fulton" <hal9000@...>
Date: 2003-03-12T09:26:21+09:00
Subject: Re: Threads and DRb

----- Original Message -----
From: "Brian Candler" <B.Candler@pobox.com>
To: "ruby-talk ML" <ruby-talk@ruby-lang.org>
Sent: Tuesday, March 11, 2003 5:45 PM
Subject: Re: Threads and DRb


> In the end, because I needed a pattern which distributed requests amongst
> multiple objects, I came up with the attached solution. It lets you create
a
> pool of objects, and you can pass the object representing the pool to a
DRb
> server (or a SOAP server, or any server which runs concurrent threads on
the
> same object). Incoming method calls are parcelled out to the individual
> objects, and no object handles more than one request at a time.
>
> I'd be interested in any comments on the attached solution (especially
flaws
> that I've overlooked); if it is sound then I'll stick it up on the Wiki.

That's pretty interesting.

I take it this solves threading and pooling at
the same time, and it's transparent from the
client end?

I"m a little fuzzy on the details of how
it works. Do you feel like clarifying?

For example: Does every object have to have
alive? and suicide methods, or is this just
an example? Why is alive? defined in the
module? If these two methods are just for
example purposes, how do we determine in
general when a pool entry is usable or
active or whatever?

Thanks,
Hal