Package: xtightvncviewer Severity: wishlist Hi Struan
Thanks a lot for this suggestion. I'm making a wishlist bug of it. On Mon, Nov 06, 2006 at 09:21:44PM +0000, Struan Bartlett wrote: > Hi Ola, > > I have a patch for xtightvncviewer that dramatically speeds up display > on low bandwidth connections. I believe it confers a real advantage for > people using modems and mobile phones for Internet access, and I would > really like to share it... but, because the tightvnc developers are > "migrating to the VNC4-derived codebase" they decline to take anything > except bugfixes! I would attempt the same patch for VNC4-based code, but > considering the scale of the changes between VNC3 and 4 this would take > more time than I have right now. Hence, I am writing to you to find out > if you might be able to integrate it into the Debian xtightvncviewer > package. I see. I'm interested but there are two complicating factors. 1) etch is about to be released and I can not apply to it before that. 2) I can apply it later but then this feature may be removed when I go up to a later tightvnc source, when they switch to vnc4 codebase. > Here is my original posting to the tightvnc developers' mailing list: > > "I've been using tightvnc among other vnc viewers for several years now. > Has anyone else found that, over slow connections, it's frustrating and > unnecessary that when the vncviewer window needs to be repainted, that > its contents need to be retransmitted again from the vnc server? Whether > over a modem or over broadband to distant machines, repainting the > viewer window this method can take valuable seconds, especially if the > server is transmitting a jpeg or complex graphic. To address this > concern I've patched vncviewer to make use of the 'image' XImage as a > backing store. This makes repainting the vncviewer window practically > instantaneous. A really nice feature! > It's a simple enough patch (although not yet compatible with the soft > cursor modes). As many operations were already written to the 'image' Hmm that may be a problem to include... > XImage buffer before being copied to the display, it seems to be enough > to: a. ensure all remaining operations (the XFillRectangles) are written > to the 'image' buffer too; b. have the Expose events cause the 'image' > buffer to be recopied to the display (using XPutImage or XShmPutImage as > appropriate) instead of calling SendFramebufferUpdateRequest every time. > > Is anyone interested in trying this patch out or including this kind of > functionality in tight vncviewer? If so, I'd gladly put it into a > suitable form for circulation to the list." > > The patch, and patched binary .debs, can be found at > http://www.praguespringpeople.org/Software/VNC/tightvnc-1.2.9-backing-store/ > > Is this anything you or anyone else can do anything with? Good to see that it compiles as works for you. Regards, // Ola > Kind regards, > > Struan Bartlett > > -- --- Ola Lundqvist systemkonsult --- M Sc in IT Engineering ---- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | http://opalsys.net/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
