> Wait a minute here. If you have to "log out and log back in again"
> around each transfer then you're doing something wrong. SSH, like rsh
> before it, and even FTP, works perfectly fine, in parallel with your
> current login session. It should be possible to invoke it from either
> end
..
> This should all be possible even if you're connected to your local
> computer with a "dumb" terminal.
It _should_ be possible .. that is the nature of my arguement. If it is
possible, I've never seen documentation of how.
> Of course if you've got any kind of
> multi-"window" environment at your "workstation" then you should be able
> to have one or more a command-line sessions running on each end (even
> with multiple slogin connections!), and life will be even more exciting
> and versatile (and of course this kind of environment can be emulated
> using job control or tools such as screen on Unix clients).
Of course. This is _not_ the point. The point relates to multiple file
transfers over a single connection. Why can't I use my existing connection
to perform this transfer?
> SSH is a _network_ tool, not a modem tool. It need not be restricted to
> opening one connection at a time or even to transfering one file at a
> time (that's just a limitation of bandwidth and latency).
Indeed, it need not. But if it isn't limited to transfering in sessions
distinct from the login session, please let me know what I'm missing.
--
Joe Rhett Systems Engineer
[EMAIL PROTECTED] ISite Services
PGP keys and contact information: http://www.noc.isite.net/Staff/
