Features/TigerVNC

From FedoraProject

< Features
Revision as of 19:15, 10 December 2008 by Poelstra (Talk | contribs)

Jump to: navigation, search

Contents

Replace RealVNC by TightVNC

Summary

Make TightVNC the default VNC client in Fedora.

There was no update from RealVNC upstream since May 18 2006 and upstream is focused on their enterprise non-open vnc. Trunk TightVNC is RealVNC fork with many improvements/bugfixes so it makes sense to use it. Main problem is that current Fedora vnc has also many changes so patches have to be merged.

Owner


Current status

  • Targeted release: Fedora 11
  • Last updated: 2008-10-17
  • Percentage of completion: 80%
  • tightvnc package has been built in dist-f11 tree

Detailed Description

TightVNC has successfully implemented "Tight" protocol enhancements which save bandwidth and are generally better than the original RealVNC's RFB 3.8 protocol. On the other hand Fedora vnc has by far a much better server (Xvnc) which is based on X 1.5 and supports more extensions. Fedora changes have to be carefully merged to TightVNC upstream and then we will use it as default Fedora vnc system.

Benefit to Fedora

vnc will have more features and will get benefit from upstream development instead of the current one man show in Fedora CVS. Overall quality should be better.

Scope

Merge Fedora changes to upstream and make TightVNC ready for Fedora

Test Plan

  • Check that libvnc.so module to Xorg works fine
  • Check that vnc installation works as expected
  • Check that viewer works fine when you connect to Xvnc and to different servers (vino)
  • Check that Xvnc works with other viewers (vinagre)

User Experience

  • Better encodings save bandwidth and processor time
  • Viewer internationalization
  • IPv6 support

Dependencies

Anaconda has to use tightvnc package instead vnc

Contingency Plan

  • Use Fedora 10 codebase

Documentation

Release Notes

  • TightVNC is used as default VNC project. Package names were changed to tightvnc, tightvnc-server and tightvnc-server-module. Binary names are same as in previous version, libvnc.so module has been moved to tightvnc-server-module subpackage. Otherwise there should be no difference

Comments and Discussion

See Talk:Features/TightVNC