I want to rewind a little.
In the his post [mailto:[EMAIL PROTECTED]] made a proposal that could the
the good enough solution many of us could live with. He made several
suggestions but the one I liked best requires a utility on the server side
and a utility on the client side. One utility reads a file, turns it into a
text format that will survive cut and paste (uuencode is one possibility)
and thens put this text representation onto the clipboard. VNC already moves
the clipboard from one side to the other. So at the other end is another
utility that reads the clipboard, decodes the text representation and
creates the file. The format can include permission data etc.
The user basically runs the utilities on first one system and then the other
and the file is transferred. It requires no extensions to VNC because
passing the clipboard back and forth is already supported. That two step
process is slightly awkward but I can easily live with it.
There are design issues over the file format that would need to be
addressed. For example the header would need to be powerful enough to be
useful in Mac, UNIX and Windowz platforms. One might want to specify a
multiple file format. On systems that support it drag and drop could be
added. If it was done cleanly enough it the VNC team might eventually
consider bringing it inside.
Does anyone else like this idea as much as I do?
---------------------------------------------------------------------
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
---------------------------------------------------------------------
