The single feature people might care about for VNC is the capability to do "desktop sharing" with it as well ( for example), I don't believe NX will do that. VNC is more wide spread and more people have experience with it.
Responsiveness varies depending on what you are doing compared to VNC, as it has to be said that nobody will be streaming video across either. I believe it has something to do with the client-side font installation. In my experience, NX is slightly more flexible than VNC sessions however I have found that really old X applications will suffer for some reason I have a backup management program that doesn't display certain information in NX that it will in VNC. NX has options which can make it more responsive across lines which are slower and have higher latency, these can be selected by the client before connections are made. Like VNC, NX can be configured so that the client can disconnect from the NX session and reconnect later (and from alternate locations). The user then runs a "client" program that connects to the server, and the server uses its protocol to send the display back to the client and receive input from the server.
In both the case of VNC and NX, the "server" component has a X-like display that the local programs attach to and treat like it was an X display. Highly simplified answer: it is more like VNC, where there is a "server" component running on the system running the desktop, and a "client" component running on the system where the user is.
0 kommentar(er)
