In Files

  • rinda/rinda.rb

Parent

Object

Rinda::TupleSpaceProxy

TupleSpaceProxy allows a remote Tuplespace to appear as local.

Public Class Methods

new(ts) click to toggle source

Creates a new TupleSpaceProxy to wrap ts.

 
               # File rinda/rinda.rb, line 257
def initialize(ts)
  @ts = ts
end

Public Instance Methods

notify(ev, tuple, sec=nil) click to toggle source

Registers for notifications of event ev on the proxied TupleSpace. See Rinda::TupleSpace#notify

 
               # File rinda/rinda.rb, line 296
def notify(ev, tuple, sec=nil)
  @ts.notify(ev, tuple, sec)
end
read(tuple, sec=nil, &block) click to toggle source

Reads tuple from the proxied TupleSpace. See Rinda::TupleSpace#read.

 
               # File rinda/rinda.rb, line 280
def read(tuple, sec=nil, &block)
  @ts.read(tuple, sec, &block)
end
read_all(tuple) click to toggle source

Reads all tuples matching tuple from the proxied TupleSpace. See Rinda::TupleSpace#read_all.

 
               # File rinda/rinda.rb, line 288
def read_all(tuple)
  @ts.read_all(tuple)
end
take(tuple, sec=nil, &block) click to toggle source

Takes tuple from the proxied TupleSpace. See Rinda::TupleSpace#take.

 
               # File rinda/rinda.rb, line 271
def take(tuple, sec=nil, &block)
  Port.deliver do |port|
    @ts.move(DRbObject.new(port), tuple, sec, &block)
  end
end
write(tuple, sec=nil) click to toggle source

Adds tuple to the proxied TupleSpace. See Rinda::TupleSpace#write.

 
               # File rinda/rinda.rb, line 264
def write(tuple, sec=nil)
  @ts.write(tuple, sec)
end

Commenting is here to help enhance the documentation. For example, code samples, or clarification of the documentation.

If you have questions about Ruby or the documentation, please post to one of the Ruby mailing lists. You will get better, faster, help that way.

If you wish to post a correction of the docs, please do so, but also file bug report so that it can be corrected for the next release. Thank you.

If you want to help improve the Ruby documentation, please see Improve the docs, or visit Documenting-ruby.org.

blog comments powered by Disqus