![]() Full documentation and complete man pages.In both windowed and full-screen modes, automatic desktop resizing chooses a server-side screen layout that honors the client's screen boundaries and taskbar/menu bar location.Allows the user to remotely configure any multi-screen Xinerama layout on the server, or to specify a multi-screen layout using the server's -geometry argument.Automatic selection of single-monitor or multi-monitor spanning based on the remote desktop resolution.Allows the user to specify whether a non-full-screen viewer window should span one or multiple monitors.Supports offset monitors and monitors with differing resolutions.More configurable and flexible full-screen and multi-screen support.Support for the full-screen application feature in OS X/macOS 10.7 "Lion" and later.Provides a toolbar for easy access to common features.Uses the system's look & feel rather than FLTK.More attractive and feature-rich VNC viewer GUI.User access control lists (for sharing sessions with specific users).One-time password support (useful when building web portals around TurboVNC).The ability to set global security/authentication policies for a particular server machine (including disabling clipboard transfer and reverse connections, limiting the remote desktop size, requiring SSH tunneling, and disabling particular authentication methods).Users can start/stop VNC sessions (TigerVNC sessions must be started/stopped by the system administrator).Dynamic VNC display number assignment (TigerVNC requires VNC display numbers to be statically assigned to user accounts by the system administrator).Multiple simultaneous VNC sessions under the same user account.Very stable - has been enterprise-tested and productized since 2004 and has thousands of seats in large corporations and academia (read more about our success stories here.).The following summarizes the strengths of TigerVNC and TurboVNC, from an end user's point of view. Thus, with the release of TigerVNC 1.2.0, The VirtualGL Project stepped down as a contributor and supporter of TigerVNC in order to focus on moving TurboVNC forward. In general, there was also just an irreconcilable clash of project management styles. ![]() Furthermore, there was resistance to including some of TurboVNC's 3D-specific features, such as automatic lossless refresh, in TigerVNC. Unlike TurboVNC, TigerVNC is not focused on 3D and video applications, so its developers were not generally very concerned with making such applications performant by default. Throughout 20, The VirtualGL Project contributed many hours of labor (probably half of them pro bono) to the development of TigerVNC, in hopes of turning TigerVNC into "TurboVNC 2.0." Ultimately, however, it became apparent that, both from a technological and a political point of view, making TigerVNC into a TurboVNC work-alike was going to be like fitting a square peg into a round hole. The TigerVNC Project was founded by some of the former TightVNC developers, Red Hat, and The VirtualGL Project in early 2009, with the goal of providing a high-performance VNC solution based on the RealVNC 4 and X.org code bases.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |