No one was asking for a SMTP, IRC, gopher, . . . server, only a feature
that allows the transfer of files. It is not very simple to install a ftp
daemon on 3,000 distributed computers world wide, deal with the firewall and
security issues. Speak for yourself on that one, guy. Why get sarcastic?
Why not deal with the situation without blowing it up into extremes? It
doesn't have to be a FTP server, as someone mentioned earlier, it can just
be intertwined with the existing communication on the same port to aid in
firewall issues.
Who cares about a single diskette? Isn't your pocket big enough for two?
Why carry a network utility like VNC around on a diskette when you can place
it on the network, anyways? We live in an age of gigabit per second LANS, a
few hundred kilobytes is not going to hurt anyone. I guess that I don't
understand why people that won't even be writing a line of code are fighting
this so much like it is going to put them out of something. Other than the
fact that it won't fit on your floppy, what is it to you if this capability
is placed in the program? What are you worried about? You don't even have
to use the version that would do this!
So far, all that I am seeing are arguments that this is not what VNC does
(yea, really, that's why people are asking for it), or it'll make the
program bigger (boohoo), or it'll create a security risk (not if people that
don't know how to secure their networks can turn the feature on or off).
In all of this I've hear a lot of people speaking for the folks at AT&T,
but I don't see them saying anything about this subject. I'm interested
what Wez has to say about this suggestion. If it doesn't happen, it doesn't
happen and people can use www.gotomypc.com or something to get the job done
and VNC can stay with the people that feel like Michael.
That is not all
-US
PS forgive me if I come off a little harsh, I'm just a bit aggrivated by
this whole thing. I don't mean to personally attack anyone here.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Michael Erdely
Sent: Tuesday, March 13, 2001 6:11 PM
To: [EMAIL PROTECTED]
Subject: Re: FTP Server
The purpose of VNC was never to provide file transfer capabilities. One of
the nice things about VNC is the ability to fit both the server and the
client (if you choose not to use the web browser) onto a single diskette if
necessary.
But, why stop at an FTP server? Heck, why not add SMTP, IRC, Gopher, . . .?
If you really must have file transfers and are using almost anything but
Win9x, it's VERY simple to install an FTP server.
That is all,
-ME
----- Original Message -----
From: "Steve Bostedor" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, March 13, 2001 5:39 PM
Subject: RE: FTP Server
> I just think that installing a separate FTP program on all of the
computers
> that I administer is a ridiculous idea. Why not let it be part of VNC
with
> an option to shut it off for those of you that don't want it. I don't see
> the reason for all of the venomous resistance to this if you can turn the
> feature off. All of the competing products do this, why hold VNC back?
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of David Rothman
> Sent: Tuesday, March 13, 2001 1:52 PM
> To: [EMAIL PROTECTED]
> Subject: Re: FTP Server
>
>
> 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
> ---------------------------------------------------------------------
> ---------------------------------------------------------------------
> 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
---------------------------------------------------------------------
