John Summerfield wrote:
Robert P. J. Day wrote:
On Sat, 5 Jan 2008, Steven Stern wrote:
On 01/05/2008 11:27 AM, Robert P. J. Day wrote:
| 3) on the server side, what is the purpose of the *other* ports
| associated with each listening port? that is, after i start vncserver
| listening on port, say, 5917, i can see listening ports 5817 and 6017
| suddenly active as well. what are they for?
|
The 58xx ports fire up a java version of the VNC viewer so you can
use VNC inside a web browser.
um ... so the 58xx ports are listening specifically only for
java-based VNC viewers that are being invoked from within a browser?
No, it's a java-implemented http proxy.
It's in the docs.
I'd call it an http server that offers to download a java applet that
runs on the client - it doesn't need java on the server.
Is there a 'complete' guide to VNC anyhere? Other ways of running it
include the X module that serves connections to the local console screen
and letting xinetd start login sessions/desktops on demand as
implemented in the vncts package. Are there more?
--
Les Mikesell
lesmikesell@xxxxxxxxx
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
