Applications:
Theoretically, a thin client can run practically any programme. In reality, using a particular software to its full potential in a thin customer environment can call for functionalities that are not present on the client machine.
As a result, a variety of factors influence the kinds of programmes that can be run on thin clients. the network bandwidth, the app publishing capabilities enabled by the present protocol, the thin client in question, and whether hardware accelerator is offered.
Therefore, different thin clients support various workloads. For instance, video streams are not (yet) natively supported by the VNC protocol mentioned above. With such a VNC connection, I can launch a video player at my desktop, however even on a fibre connection, it only plays at roughly 1 frame per second.
On the other hand, you may use the same network connection to run a web browser which supports Flash, link to a remote video server, and watch full-screen H.264 video playback. You may even establish a VNC connection in the web browser thanks to a Java-based web plugin that a VNC server can offer. This applet runs almost as quickly as a binary client as well as supports the majority of the capabilities.
