深入PCOIP协议.pptVIP

MYTH: PCoIP bets on UDP as the foundational transport for graphics REALITY: T... MYTH: PCoIP bets on UDP as the foundational transport for graphicsREALITY: TCP constrains Citrix ICA and Microsoft RDPWhile TCP is a great reliable transport for data traffic that is not latency sensitive and does not require constant feedback, for example file transfers, HTTP web pages which send all interactive data up-front, or streaming data that is uni-directional and does not depend on latency (i.e. media streaming with large buffers). TCP is not a great reliable transport layer for streaming a PC experience which requires instantaneous interaction and constant content updates. Using TCP limits the way in which you use the reliable transport. For specific data types, you do not need reliabiility, for example if you have 3 screen changes A,B, and C, throwing B out is perfectly fine as long as C screen change overlaps what is done in B. You cannot do this if you use TCP. So for certain types of networks (high latency) TCP actually limits you. TCP may be necessary for the Citrix ICA protocol as the data that they present is generated on the client and if you miss one screen or graphical command it could affect all subsequent graphic commands. MYTH: PCoIP claims bitmap remoting is the best way to deliver graphicsREALITY: Teradici claims host rendering with intelligent display decomposition compression is the best way to deliver desktops (Citrix Microsoft now focusing more and more on host rendering too)True Bitmap remoting isnt the best way to deliver graphics. This is why PCoIP does NOT do bitmap remoting. As discussed in other blogs, host rendering with a display decomposition layer takes the display input and determines which way to encode a specific region of the screen. So for the example above, the 400x300 rectangle with black borders and white background, this isnt sent as a bitmap. This is decomposed into a white background and a black border, and sent compressed acco