re: your bottom line...
> To put it like this, if you can get your users to embrace
VNC, and they know
> enough about computers to use it, they sure as hell know
enough to use an
> ftp program, and seriously I've seen FTP servers that are
a lot less
> complicated to configure than VNC (basically "okay which
port" and "okay
> which directory").
that's true, but what about on the fly file xfers?
1. i sometimes have the need to quickly xfer a set of files
(which r too big to move w/email). is there an easy/safe
way to do an on the fly xfer? running an ftp client is no
big deal, but to setup a server for this occasional
situation can be a pain (or it may be the case that you are
not on your home machine). for one file, one can resort to
(hold your breath) one of the IRC clients, but for a larger
set, that's not practical.. it would be nice to have some
simple program that each side can run to effectuate the
xfer.
that type of program doesn't need to be inside of VNC, but u
could use VNC to run it remotely from the client and when
done the connection would close.
----- Original Message -----
From: "Gustafsson, Bjorn" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, March 13, 2001 1:19 PM
Subject: RE: FTP Server
> Okay, I might be a bit out of line, but I still don't
(really) see the point
> of it.
>
> I understand the need for being able to transfer files
from one place to
> another, be it from home to work or whatever but picture
this scenario:
> Your sysadmin enables a user to remotely connect on an
officially unused
> port, without any authentication whatsoever to any
specific machine in the
> coorporate network, but he won't enable his users to logon
to the network
> when not physically at work, therefore not enabling them
to access printers
> and servers from home.
>
> Sure, SSH is nice, but for remote work needs, VPN looks
more like the way to
> solve the problem, not by expanding VNC (which, mind me,
is not the first
> program that a sysadmin would let loose on his network,
since it's quite
> unsafe in the basic version).
> But the bottom line is : "VNC is a remote controlling
software, if you need
> file transfers, use 3rd party program".
> To put it like this, if you can get your users to embrace
VNC, and they know
> enough about computers to use it, they sure as hell know
enough to use an
> ftp program, and seriously I've seen FTP servers that are
a lot less
> complicated to configure than VNC (basically "okay which
port" and "okay
> which directory").
>
> But anyway, sure, I wouldn't mind having an FTP server
bundled with VNC.
> With regards to my last message, I wouldn't actually mind
having any of
> those *bundled* with VNC, as long as:
>
> 1) I don't have to download them (plugins is an excellent
idea) and/or
> recompile VNC to leave them out
> 2) They won't take too much time from the actual VNC
development.
>
> The extra things requested (mainly file transfer) already
exists in various
> forms, and putting a lot of effort into mimicing one of
those is in my
> opinion quite obviously not the right thing to do, but
instead increase the
> usefulness of VNC as a remote desktop tool. Sure, if
someone came up with a
> nice file drag&drop extension to VNC I really wouldn't
mind, but actually
> suggesting implementing an FTP server seems rather screwed
to me.
>
> There has been some good ideas here lately, and I'd rather
see one of them
> implemented before an FTP server.
>
> /Bjorn
>
> -----Original Message-----
> From: Morris, Steve [mailto:[EMAIL PROTECTED]]
> Sent: den 13 mars 2001 18:06
> To: [EMAIL PROTECTED]
> Subject: RE: FTP Server
>
>
> Gustafsson, Bjorn [[EMAIL PROTECTED]] rather
annoyingly writes:
> > Sure, someone packaging VNC with
> > FTP/HTTP/SMTP/POP3/IRC/NNTP/Napster/Real/Telnet servers
> > might be a good idea
>
> Now you're being unfair. There is a real need being
discussed here. Making
> fun of people with that need does not enhance the
discussion. Nobody asked
> for "HTTP/SMTP/POP3/IRC/NNTP/Napster/Real/Telnet servers."
>
> A common VNC user will use it to access a work machine
from home, especially
> now that many of us have broadband access which makes this
workable. VNC
> alone is not enough to solve the needs of this user. An
absolutely critical
> need is secure access. This is not part of VNC. Local
printing of the remote
> files is often required. And file transfer would be nice
because VNC is not
> really adequate for extensive editing sessions. Besides
file transfer solves
> the printing problem. An integrated VNC/SSH/FTP would be a
powerful and
> useful combination to solve a single need. Most home users
of VNC will want
> that set of functionality. Asking for this set of related
functions is not
> the same as asking for Napster to be integrated.
>
> This is a nice tight set of requirements which logically
go together to
> define a useful remote access environment. It is this very
same set of
> requirements that are often asked for on this list. The
request is
> reasonable. It might not be cost effective for the VNC
team to respond to
> this request but saying "no we can't do that" is not the
same as saying
> "stupid request." You seem to be in the "that's a stupid
request" category.
>
> Remote administration is a valuable use for VNC but
represents only a subset
> of the users. I'm sure remote administators don't see the
point because they
> are quite capable of solving the additional requirements.
It should be part
> of their professional skill set.
>
> I was trying see if there was room for some middle ground
in this
> discussion.
> ----------------------------------------------------------
-----------
> To unsubscribe, send a message with the line: unsubscribe
vnc-list
> to [EMAIL PROTECTED]
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ----------------------------------------------------------
-----------
> ----------------------------------------------------------
-----------
> To unsubscribe, send a message with the line: unsubscribe
vnc-list
> to [EMAIL PROTECTED]
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ----------------------------------------------------------
-----------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
