> -----Original Message----- > The problem is that VNC, on *nix systems, will always use a > display number > for access by applications. If one drops the display number > for the VNC > client connections, then we'll have *two* unrelated IDs for > the VNC server - > the display number, and the VNC ID, whatever that might be > (port perhaps?).
This is what happens with the -init option as described at http://www.sourcecodecorner.com/articles/vnc/linux.asp. Hence, vncviewer can coop with it, as can Xvnc. According to the Xvnc options (`Xvnc --help`) all ports can be controlled. > > In the *nix world, using display number for both the > applications and the > VNC client makes sense. (Xvnc actually has three ports based on the > display number: 5800+display, 5900+display, and 6000+display. > The last one > is the port used by applications to connect to the server.) Correct me if I'm wrong but I see the next controllable optoins from the Xvnc server: 5800+display# == Web interface, serving the java applet. Can be altered with -httpport option. Only used to provide the java applet. If you have a webserver running, it can provide the same applet from a totally differnt sublocation (like http://machine/vncviewer) on a different port (80, the http default) just as long as the java applet is activated with the right port (the rfb port) See the page's html source provided by the server for details. 5900+display# == vncviewer interface. Can be altered with -rfbport option. This is the port used for communication between vncviewer and vncserver. The vncviewer should be able to read a display number or a port number. Unfortunatly, both have a similar syntax. Who adds the option -rfbport to the viewer, just as the java applet does? 6000+display# == X11 input (?) Is contolled by the display number. This is the X11 definition. It is (unfortunatly) only used in the Xvnc server, not in the winvncserver. However, I just discovered that the winvncserver with auto display number used :0 if there is no X11 server running and it is using :1 if there is a X11 server running at :0. Hence it is somehow prepared on X11 on a windows machine. This leaves the -port and -udpinputport. I don't know them but I think it's something with X11, not with VNC. > > I agree it doesn't make much sense in the Windows-only world; > however, when > connecting to *nix systems (from any system) it does make > sense, and (in my > opinion) should not be removed. As far as I can see now, it is not used at all within the vnc protocol > > Perhaps what we need is a way to explicitly specify the VNC port (the > 580x/590x) on both the client and server. Connections to > non-*nix systems > could then use that. As above, the Xvnc server can and the java applet can. > > According to Alex K. Angelopoulos: > > OK, let's drop the word "traditional" then. > > > > Let's make it: > > "I would dearly love to see a method of dealing with > display and port > > numbers which does not confuse the bejeezus out of new users." > > > > Follow-ups | /dev/null > > > > ----- Original Message ----- > > From: "Scott "The Axe" O'Bryan" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Tuesday, 2002-03-19 19:28 > > Subject: RE: The Next Generation display numbers > > > > > > : I think it was taken off of the Unix display model, which > some would > > : argue IS the traditional way of exporting a display. :) > Just food for > > : though. > > : > > : -----Original Message----- > > : From: [EMAIL PROTECTED] > > : [mailto:[EMAIL PROTECTED]] On Behalf Of Alex K. > > : Angelopoulos > > : Sent: Tuesday, March 19, 2002 10:30 AM > > : To: [EMAIL PROTECTED] > > : Subject: VNC:The Next Generation display numbers > > : > > : FWIW, if this hasn't been discussed - I would dearly love > to see VNC go > > : to a > > : more "traditional" approach in numbering displays - e.g., > using a port > > : number for specification of ports used instead of an > arbitrary display > > : number based on 5900... this causes too many headaches. > > : > --------------------------------------------------------------------- > > : To unsubscribe, mail [EMAIL PROTECTED] with the line: > > : 'unsubscribe vnc-list' in the message BODY > > : See also: http://www.uk.research.att.com/vnc/intouch.html > > : > --------------------------------------------------------------------- > > : > --------------------------------------------------------------------- > > : To unsubscribe, mail [EMAIL PROTECTED] with the line: > > : 'unsubscribe vnc-list' in the message BODY > > : See also: http://www.uk.research.att.com/vnc/intouch.html > > : > --------------------------------------------------------------------- > > > --------------------------------------------------------------------- > > To unsubscribe, mail [EMAIL PROTECTED] with the line: > > 'unsubscribe vnc-list' in the message BODY > > See also: http://www.uk.research.att.com/vnc/intouch.html > > > --------------------------------------------------------------------- > > -- > > Grant McDorman <[EMAIL PROTECTED]>, Sr. Software > Design Consultant > Cedara Software Corp. <URL:http://www.cedara.com> > (formerly I.S.G. Technologies Inc.) > Mississauga, Ontario, Canada > > [demime 0.97b removed an attachment of type application/pgp-signature] > --------------------------------------------------------------------- > To unsubscribe, mail [EMAIL PROTECTED] with the line: > 'unsubscribe vnc-list' in the message BODY > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
