From: Peter Ertl <pertl@...>
Date: 2006-03-23T19:49:56+09:00
Subject: Re: drb over pipes

the 'daemon' is just ssh which you already have. 
there will be no additional executables when you use tunneling, 
just secure shell on port 22 (or whatever). tunneling is configured
in the client and can be allowed/forbidden on the server side.

> --- Urspr�ngliche Nachricht ---
> Von: Reto Schuettel <reto-ruby-talk@schuettel.ch>
> An: ruby-talk@ruby-lang.org (ruby-talk ML)
> Betreff: Re: drb over pipes
> Datum: Thu, 23 Mar 2006 19:24:03 +0900
> 
> Hi 
> 
> On Thu, Mar 23, 2006 at 07:01:35PM +0900, Yoann Guillot wrote:
> > On Thu, Mar 23, 2006 at 06:42:49PM +0900, Reto Schuettel wrote:
> > > At the end of the day I'd like to do something like that:
> > >   # ruby client.rb | ssh host 'ruby agent.rb'
> > > 
> > 
> > With drb, the client needs to talk to the agent and vice-versa, so this
> > command line will never work (the client will talk to the agent, but not
> the
> > other way around).
> 
> A pipe provides two streams (in & out), and tcp does the same. The
> question is now if drb really needs two connections (-> 4 streams)?
> 
> > > Unfortunately using drb's tcp protocol directly isn't really an option
> in
> > > our environment.
> > > 
> > > Does anybody have a good idea? 
> > 
> > As suggested, tunelling is probably the best/simpler choice.
> 
> Tunneling may be a solution, although I'd prefer the pipe. Otherwise
> there would be a daemon, somewhere listening on localhost:port. 
> 
> Regards,
> Reto Sch�ttel
>