Bug in Rinda (Drb 2.0.4)?

ruby-talk
1

I’m working on figuring out the ins and outs of using Rinda and TupleSpaces
with DRb, and I think I’ve ran across a small bug in Rinda::TupleSpaceProxy.

The read_all method looks like this:

def read_all(tuple)
@ts.read_all
end

The problem here is that TupleSpace’s read_all method is defined as:

def read_all(tuple)

so we get ArgumentError from a call to Rinda::TupleSpaceProxy.read_all.

The fix, which seems to work, is to just change it to this:

def read_all(tuple)
@ts.read_all(tuple)
end

Thanks,

Kirk Haines

2

Hi, Kirk.

···

On 2004/05/06, at 19:26, Kirk Haines wrote:

The read_all method looks like this:

def read_all(tuple)
@ts.read_all
end

The problem here is that TupleSpace’s read_all method is defined as:

def read_all(tuple)

so we get ArgumentError from a call to Rinda::TupleSpaceProxy.read_all.

The fix, which seems to work, is to just change it to this:

def read_all(tuple)
@ts.read_all(tuple)
end

This is fixed in CVS.
see:
http://www.ruby-lang.org/cgi-bin/cvsweb.cgi/ruby/lib/rinda/
rinda.rb.diff?r1=1.1;r2=1.2;f=h

3

This is fixed in CVS.
see:
http://www.ruby-lang.org/cgi-bin/cvsweb.cgi/ruby/lib/rinda/
rinda.rb.diff?r1=1.1;r2=1.2;f=h

Great. Is the CVS version stable? I’m looking at starting on, today, a
project using DRb/Rinda/TupleSpace for the architecture of a distributed
application. I think I’ve figured out enough about how it all works to do
what I want.

Thanks,

Kirk Haines