>> (Seriously, a VNC-server-provided FTP server is a really bad idea,
>> IMHO.)
>
>I agree, but I'll confess that I prefer the Unix toolbox approach; create a
>bunch of simple tools that each do one thing well, and chain them together
to
>make more complicated stuff. The applications and protocols for VNC and FTP
>are totally separate. There's not anything that could be shared between
>them. I can't see anything that'd be gained by bundling them both into one
>executable.
Consider the following scenario:
A tech support worker, behind a corporate firewall, accesses a user's PC
which is behind another corporate firewall. These firewalls are pretty
tight, and the only way the tech support worker has access to the user's
machine is through a single, dedicated VNC port or tunnel set up
semi-automatically via scripts running on the bastion hosts.
The support worker diagnoses that a software update is required on the
user's PC, but the user is not qualified to install it. The worker cannot
reach the user's machine physically because it is 100 miles away. The
remote site support staff are off duty, but the user has an approaching
deadline to meet. Since the firewalls are both tight, the support worker
cannot use external tools, such as FTP or HTTP to send the required
software to the user's machine.
In this case, probably the only way to get data across is to use
data-transfer tools built into VNC itself. Probably this is exactly why
products like PC-Anywhere gain market share in the corporate sector,
because they provide the little, essential tools like this and integrate
them into the package seamlessly. In fact, this is a *classic* example of
where integration is a Good Thing - where limited resources are available.
If some people don't like having extra "bloat" in VNC, here's some tips:
- Don't use it. Disable the functions if you have to.
- Recompile it yourself, without the "extra bloat".
- Make your recompiled version available for download, stating clearly that
it's a cut-down version for smaller downloading.
You are perfectly entitled to do all this. But do you already bother to do
so with the HTTP server and Java applet built into VNC servers at this
moment? If not, stop complaining. Please.
--------------------------------------------------------------
from: Jonathan "Chromatix" Morton
mail: [EMAIL PROTECTED] (not for attachments)
big-mail: [EMAIL PROTECTED]
uni-mail: [EMAIL PROTECTED]
The key to knowledge is not to rely on people to teach you it.
Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/
-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
-----END GEEK CODE BLOCK-----
---------------------------------------------------------------------
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
---------------------------------------------------------------------
