monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Monotone-devel] Re: Anybody working on SSH (aka stdin/stdout) suppo


From: Christof Petig
Subject: Re: [Monotone-devel] Re: Anybody working on SSH (aka stdin/stdout) support for netsync
Date: Mon, 17 May 2004 10:01:57 +0200
User-agent: Mozilla/5.0 (X11; U; Linux ppc; de-AT; rv:1.6) Gecko/20040414 Debian/1.6-5

Herve Quiroz schrieb:
On Wed, May 12, 2004 at 11:17:31PM -0400, graydon hoare wrote:

Christof Petig wrote:

Hello,

is anybody working (or planning to work) on pipe/stdin/stdout support for netsync? I would love to have it working soon.

I am not currently working on it, but I'd love to see an implementation. I can imagine two approaches: either teach Netxx how to wrap file descriptors (quasi-sockets); or abstract netsync.cc to accept either Netxx or file descriptor versions.

either should be plausible, and would be most welcome.


Just my 0.02...

What about using SSH builtin tunnel facility? This way, you don't need
to wrap file descriptors. You just use the initial SSH connection to
setup the tunnel and negociate through stdin/stdout about potential
additional parameters (like port number in case this one is already in
use). Then everything related to netsync happens over the tunnel.

Using stdin/stdout avoids opening a port on the server and running a daemon. Secure shell access is all you need (no running daemon, no port).


As for command-line parameters, why not using URLs (with a protocol://
prefix)? This could even allow a "pull" to occur between two distant
databases (for which I have yet to find a relevant use case actually).

Do you have an example on how you would phrase the two usages of monotone (client+server) for sync via ssh? I thought about URLs but did not want to touch the current syntax.

   Christof




reply via email to

[Prev in Thread] Current Thread [Next in Thread]