FYI, Dimensions for use with the XRANDR extension are specified to the
standard Xvnc server via the "-randr" parameter, followed by a
comma-separated list of <width>x<height>, each optionally followed by a
[<X-millis>x<Y-millis>] term. This is available in VNC Enterprise Edition
servers at present.
Wez @ RealVNC Ltd
> -----Original Message-----
> From: vnc-tight-devel-bounces@...
> [mailto:vnc-tight-devel-bounces@...] On
> Behalf Of George Wright
> Sent: 03 September 2008 10:25
> To: vnc-tight-devel@...
> Cc: Peter Astrand
> Subject: RandR in TightVNC - client initiated protocol suggestions
> I'm currently working on implementing RandR support in
> TightVNC 1.5-xserver, and I've forward ported a patch for an
> older version of VNC .
> This seems to work as expected; you pass multiple -geometry
> flags to Xvnc and they're all listed by xrandr in the
> session. xdpyinfo says the RANDR extension is present, and
> xrandr -s allows you to switch the resolution of the VNC
> session, and vncviewer reacts by resizing its window accordingly.
> However, I'd like to do better than this, by allowing the
> client (vncviewer) to request a resolution change from the
> server. This could be, for example, so that the vncviewer
> window is made resizeable, then resizing it would cause it to
> request a resolution change on the server, to which Xvnc
> replies by adding the requested resolution to the list of
> supported RandR resolutions then switching to it.
> Looking at the RFB protocol , I have come up with the
> following rough outline of how this could be done. Note that
> I'm not particularly familiar with RFB so any comments would
> be appreciated.
> - Use the DesktopSize pseudo-encoding to enable/disable RandR
> at the server if the client can't support it
> - Add a Client-to-Server message called SetDesktopSize:
> No. of bytes | Type [value] | Description
> 1 | U8 TBC | message-type
> 2 | U16 | framebuffer-width
> 2 | U16 | framebuffer-height
> The protocol says that the client must receive an
> extension-specific confirmation that the server supports the
> extension, but does not state if there is a canonical way of
> doing this. Is it just a case of writing a server-to-client
> "pseudo encoding" called, for example, "DesktopResizeable"?
> [1 ] -
>  - http://www.realvnc.com/docs/rfbproto.pdf
> George Wright, http://www.gwright.org.uk