----- Original Message ----- From: "Beerse, Corni" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, 2002-05-21 03:01 Subject: RE: File Transfer with WinVNC?
(SNIP) > I hate those piggyback things. A tool has to do what it is good at and > nothing more. (SNIP) > > If you're thinking about plugin's, take an other tool and use vnc as a > plugin! For the current available stuff, you can create a setup as follows: > > On the vncserver machine, also start the ftp server. > On the viewer side, use netscape as base of the viewer: > View at http://vncviewer:5800/ > file transfer (in a new window) at ftp://vncviewer/ > > and off you go. > You know, this is actually a profoundly important point. One of the things that has been bugging me for a while is the fact that there does need to be some mechanism for allowing simple file transfer in almost all full-featured remote control tools. The problems with doing this with VNC are varied; it would introduce reliability issues, most of the Unix VNC people don't *need* it, and there would be further proliferation of source code variations. Since VNC is doing exactly what it needs to as far as remote GUI interaction goes - yeah, why "break" it by extending it? Using some sort of external tool to integrate remote sessions would be a little more robust, and let people take an a la carte approach: if you don't want it, don't use it. If you're a VNC GUI developer, don't worry about file transfer; it's something else. Seamless, secure ad-hoc file transfer is a useful capability, but it does make more sense to have such a product architecturally completely separate from VNC, even if it is somehow presented to the user in such a manner that it *appears* to work with VNC. --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
