We begin our discussion by clarifying that vnc is not a program. Rather, we are talking about a protocol,
or a “language of communication” that must be implemented (or “understood”) by the specific software you want to provide access capabilities through this technology.

Originally created at Olivetti & Oracle Research Lab (ORL), source code and vnc specifications of Virtual Network Computer vnc have been been publicly released,
promoting the proliferation of parallel implementations (all but compatible) more and more equipped.

Among the most significant, we might remember that the Real vnc , a company founded by the original developers, TightVNC,
an open source project aimed at narrow-band connections, and Ultra vnc , which also comes under a free license but with many additional features compared to competitors .

Precisely because of the larger dowry that comes with Ultra vnc , specifically in the article we will refer to this implementation.

As already mentioned, however, the various implementations of vnc are all compatible with each other: this means that a client has, for example,
UltraVNC will connect to a remote computer which could perform RealVNC or vice versa.

Read the full story here A protocol, not a program vnc
More detail from here A protocol, not a program vnc