Features/TigerVNC

Replace RealVNC by TightVNC

Summary

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 using it. Main problem is current Fedora vnc has also many changes so sources have to be merged together.

Owner

• Name: AdamTkac

Current status

• Targeted release: Fedora 11
• Last updated: 2008-09-30
• Percentage of completion: 75%

- main task (merge our Xvnc changes to upstream) is already done, package awaits for review

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 and goes hand to hand with upstream X development. 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

Requires merging Fedora patches to upstream

Test Plan

• Push TightVNC based vnc to rawhide as soon as possible and users will test it

User Experience

• Better encodings save bandwidth and processor time
• Improved keyboard handling when server and viewer uses different keyboards
• Viewer internationalization

Dependencies

Anaconda has to use tightvnc package instead vnc

Contingency Plan

Use Fedora 10 codebase

Documentation

None needed

Release Notes

Not needed

Comments and Discussion

See Talk:Features/TightVNC

---