Exceed onDemand A Technical Whitepaper

More documents

Recommendations

Info

Exceed onDemand 5 — A Technical Whitepaper Figure 4 — Connects to X applications through an Exceed onDemand Server Thin X Protocol History X Window System was developed in 1984. The goal was to create an operating environment that was truly hardware and vendor independent. The protocol that it used was called X protocol. It was designed to run on a Local Area Network (LAN) where bandwidth was high and latency was low. However, the terms “high bandwidth” and “low latency” can rarely be used to describe Wide Area Network (WAN) or Internet connections. A new protocol is urgently needed in order to create a server-based PC X server that can efficiently link the client to the server over any type of network connections, hence the birth of Thin X Protocol (TXP). 16 X Application X Application X Application X Protocol Traffic X Protocol Traffic Exceed onDemand Server Thin X Protocol Traffic Thin X Protocol Traffic Exceed onDemand Client Exceed onDemand Client Exceed onDemand Client
What is TXP? TXP is designed to: > Exceed onDemand 5 — A Technical Whitepaper > Split functionalities between the Proxy and Client — The X functionalities are split between Exceed onDemand Proxy and Exceed onDemand Client, because the Proxy does not have the native ability to handle drawing requests and keyboard and mouse inputs. These requests are mapped to the TXP-equivalent requests and passed between Clients and Proxies. > Reduce bandwidth requirement — TXP has the ability to compress, cache and optimize requests. The goal is to minimize the amount of data that has to travel across the high latency, low bandwidth network. The trade-off for compressing the requests is higher CPU overhead; additional CPU cycles and computer resources are required to compress and decompress the requests. However, the abundant CPU power that PCs and servers now harness allows Exceed onDemand to achieve higher compression rates without sacrificing computer performance. > Adapt to the network bandwidth — The level of compression and optimization can change automatically depending on the network bandwidth availability. As the available bandwidth decreases, the compression increases and special optimization of TXP is activated. The shift between CPU overhead and bandwidth usage is done automatically during startup without involving the user. > Reduce roundtrip requests — X applications normally communicate with an Exceed onDemand Proxy over a LAN connection where network bandwidth is abundant. Exceed onDemand Proxy, acting as a fully functional X server, is capable of handling all X protocol commands with the exceptions that have already been mentioned. As a result, many of the roundtrip requests are taking place over a LAN connection with little latency, while few roundtrip requests take place over WAN or Internet connections using the bandwidth-friendly TXP. Comparing this to a traditional X server running on a WAN or the Internet, where all X protocol commands have to travel on low bandwidth connections, the reduction in the number of roundtrip requests over the WAN or Internet connection is significant, thus giving Exceed onDemand an unparalleled performance advantage. > Strengthen X security over WAN and Internet — TXP can be easily encrypted using Secure Sockets Layer protocol for heightened security. 17
Page 1: Transforming Information into Intel
Page 4 and 5: Exceed onDemand 5 — A Technical W
Page 62: Server > Desktop Consolidation > X

Exceed onDemand A Technical Whitepaper

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?