ssh lets you set up port forwarding in both directions. It works fine,
although of course you have to set up the ssh connection yourself
first.
i don't *think* that's true. certain operations in drb will cause a
*new* connection to be opened up on a *new* port. it's not the bi-
directionality that kills you, it's that you cannot know which ports
drb will use in advance. it's been a while since i played with this
but block methods, iirc, involve opening up a new connection on an
unknown port
http://groups.google.com/group/ruby...96b0?hl=en&lnk=gst&q=drb+ssh#3efaa1c9e9c896b0
possibly i'm wrong, but i played with this for quite a while and,
while i could get simple methods working but not complex ones. i
think the testcase to use is
remote_object.each do |remote_element|
remote_element.method
end
the block cannot be serialzed so the remote_object has to call back to
the client on a *new* connection - and that's where things get messy.
hopefully i'm wrong.
cheers.
a @
http://codeforpeople.com/