REALITY: Teradici claims host rendering with intelligent display decomposition and compression is the best way to deliver desktops
Bitmap remoting is NOT the best way to deliver graphics. This is why the PCoIP protocol does NOT do bitmap remoting. Instead, the PCoIP protocol uses host rendering to generate the entire display image at the server/workstation in the datacenter. A display decomposition layer then selects the proper CODEC for encoding each region of the screen. So, for example, a 400×300 rectangle with black borders and white background is not sent as a bitmap. This is decomposed into a white background and a black border and compressed as a two-color object that is just as efficient as a RECT command with coordinates. As another example, in most cases, a text-based web page encoded using the PCoIP protocol compresses into the same amount of data or less than sending the HTML for that given web-page. PCoIP algorithms include intelligent rendering functions wrapped into its encoding scheme.
For client rendering protocols like RDP and ICA/HDX, many years of fine-tuning are required to deal with all of the different graphic primitives of OpenGL, DirectX and whatever may come (e.g.. Web3D, HTML5, ON2 …). However, by generating all of the pixels at the host and using intelligent decomposition, the PCoIP protocol is independent of all the different graphics APIs. This graphics independence has allowed Teradici to spend all if its time and effort on how to properly encode the data to provide the best user experience. The PCoIP protocol has five+ years of fine-tuning already under its belt and will continue to improve in the future.