From: Aredridel <aredridel@...>
Date: 2003-05-15T02:23:46+09:00
Subject: Re: RCR for child execution

On Wed, 2003-05-14 at 04:40, Simon Strandgaard wrote:
> Besides that I want this 'permanent sandbox' myself. I think that its a 
> very useful for other people which embeds ruby into c++. There has been
> very opinions from this embedding-camp so far. Therefore I think this is
> worth figthing for.
> I would like to hear opinions: Is this usable ?

Simon -- I think one thing that would do what you want is a solution
with dRb and proxy objects.

using dRb would make the objects seem to be local to the process, when
in fact, they're in another (socket-connected) process.  Extending dRb
to use pipes should be trivial, too, and would be a little cleaner.

Your process and the scripts-and-children could then have separate ins
and outs.

Particularly for your application, at least under unix, using PTYs to
get the I/O in and out of your child processes would be smart -- that's
why terminal emulators use the PTY system.  It would be a very workable
solution, I think, and isolating Ruby into it's own process for such
scripts would also fix interdependency problems with native threads.

Though it /sounds/ kludgy, I think it may end up being a more stable
solution that is more portable.

Ari