>I use VNC for a variety of purposes, and I very often find it necessary to
>bring back a file. Sometimes because we're using VNC for support
>(trouble-shooting) purposes and we need to bring back diagnostic
>information. Sometimes we generate printed output and we want to bring the
>spoolfile back to print it locally. I suspect that for every situation in
>which remote control is useful, one finds a directly related need to
>transfer files. And I mean the file transfer need arises directly out of
>the work being done in a remote control session.
This is exactly my view. After making N SSH tunnels just to be able to
access my computers behind their double-firewall, I want to be able to have
complete control over them - including being able to copy files around
without relying on whatever software happens to be installed on the client.
Printing is much lower on my wish-list, largely because I do much more work
in softcopy than hardcopy. It's also considerably harder to implement,
especially cross-platform. Windows can print to a spool file, if the
correct driver for the target printer is installed - this is probably good
enough for many needs, if file transfer is available.
--------------------------------------------------------------
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
---------------------------------------------------------------------
