TigerVNC

From Wikipedia, the free encyclopedia
Jump to: navigation, search
TigerVNC
TigerVNC logo.svg
Initial release February 27, 2009 (2009-02-27)
Stable release 1.3.1 / March 19, 2014; 5 months ago (2014-03-19)
Written in C, C++, Java
Operating system MS Windows (32-bit/64-bit) (NT/2000/XP), POSIX (Linux/BSD/OS X/UNIX-like OSes), MinGW/MSYS (MS Windows)
Available in English
Type Remote desktop, Remote administration, Distributed computing
License GNU General Public License
Website www.tigervnc.com

In computing, TigerVNC, a VNC server and client, started as a fork of TightVNC in 2009.[1]

Red Hat, Cendio AB and TurboVNC maintainers started this fork because RealVNC had focused on their enterprise non-open VNC and no TightVNC update had appeared since 2006.[2] TigerVNC is fully open-source, with development and discussion done via publicly accessible mailing lists and repositories.

TigerVNC focuses on performance and on remote display functionality.[3] It became the default VNC implementation in Fedora shortly after its creation.[4]

A 2010 reviewer found the TigerVNC product "much faster than Vinagre, but not quite as responsive as Remmina".[5]

See also[edit]

References[edit]

  1. ^ Peter Åstrand (2009-02-27). "Open Letter: Leaving TightVNC, Founding TigerVNC". TightVNC mailing list. Retrieved 2014-02-10. "[... W]e are now announcing the TigerVNC project. The project is based on the TightVNC /trunk source tree." 
  2. ^ Peter Åstrand (2009-02-27). "Open Letter: Leaving TightVNC, Founding TigerVNC". TightVNC mailing list. Retrieved 2014-02-11. "Recently, however, it has became clear that the TightVNC project cannot support this development. [...I]n practice, the TightVNC project was forked four years ago, when the /trunk source tree was created. The core TightVNC team mainly work in other branches. No release of TightVNC has been based on the /trunk source code and no real effort on merging the different branches has been done." 
  3. ^ "Review of TigerVNC". Podnova Windows Library. 2013-03-22. Retrieved 2013-12-02. 
  4. ^ Adam Tkac (2009-03-04). "TightVNC feature has been renamed to TigerVNC". fedora-devel-list, Development discussions related to Fedora. Retrieved 2013-12-02. 
  5. ^ Veitch, Nick (2010-09-17). "TeamViewer, TigerVNC, Vinagre and NoMachine NX". Reviews. Linux Format (136). ISSN 1470-4234. Retrieved 2014-02-10. "Of the VNC clients, it was much faster than Vinagre, but not quite as responsive as Remmina." 

External links[edit]