Darren J Moffat wrote:
> Huh ?  That still makes two to me, one which is native code and one
> which is a jar file.  It that is what vino is supposed to be then I
> think I'm fine with having both they seem to serve different purposes as
> implementations of the same protocol.

Vino is a VNC server that exports the contents of your running X session.

To allow users on machines without a local vncviewer installed to connect
to a running session, Vino and Xvnc both offer an option to listen on a
TCP port for an http connection to which they respond with an html page
embedding a Java applet client.   (They both offer up the same .jar files
from the RealVNC project for this applet.)

The previous case (2007/391) simply provided a shell script that ran
java -jar /usr/share/gnome/vino/vino-client.jar to allow use of this
applet as a standalone vncviewer.   This case replaces that with a
compiled C application which will more closely match what most other
platforms ship as /usr/bin/vncviewer.

> Does this vncviewer support SSL/TLS ?  If so which SSL/TLS library does
> it use.

No.

-- 
        -Alan Coopersmith-           alan.coopersmith at sun.com
         Sun Microsystems, Inc. - X Window System Engineering


Reply via email to