-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Jun 23, 2007 at 09:23:49AM -0300, Gerhard Fiedler wrote:
> > To clarify, unison needs a copy of unison available on the other system.
> 
> And this other copy needs either run there permanently as a service or
> needs to be started before using unison. On *ix systems this is usually
> done with SSH (which AFAIK is integrated into unison in a way that it can
> start it automatically), but on Windows systems you'd either have to set up

You're basically right, but to be a little  pedantic about it the
standard way for apps like unison to work over ssh is for the app to use
the ssh remote command mechanism.  Essentially you can have ssh run a
remote command, instead of simply giving you a shell. The most simple
example is the scp command, ssh copy. If you do the following:

scp somefile remotehost:/tmp/

You local scp process runs essentially this:

ssh remotehost scp --server-mode

Then scp sends the remote copy of scp, running in the special "server
mode" commands to do whatever is needed. Unison is implemented the same
way, along with *many* other unix utilities.

What's neat about this mechanism is it makes the code very simple.
Permissions mechanisms don't need to be implemented, ssh does that all
for you. You also don't need to run a seperate server daemon process.

- -- 
http://petertodd.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFGfdV73bMhDbI9xWQRArU5AKClhTbCtfRmO5aeQYdSq9LDhEtJRgCgsuai
aIEqDfnTSBQnK1NDVbehEBA=
=Pj3p
-----END PGP SIGNATURE-----
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist