Exceed onDemand A Technical Whitepaper
Exceed onDemand A Technical Whitepaper Exceed onDemand A Technical Whitepaper
Exceed onDemand 5 — A Technical Whitepaper Figure 14 — Exceed onDemand Server Files shows all of the available files on the Server Performance Optimization Exceed onDemand is designed to run on all types of network connections, but especially on remote connections such as WAN and Internet. The remote access connection speed varies widely, from a dial-up modem connection at 33.6kbps to a DSL connection that can be as fast as 1.5Mbps. Regardless of the connection speed, Exceed onDemand Client can efficiently communicate with Exceed onDemand Server. FAST and SLOW Connection Exceed onDemand automatically tests the connection speed when an X session is launched. Based of the results of the test, Exceed onDemand decides if the Exceed onDemand Proxy should be set to “Fast” or “Slow” Connection. This selection dictates the level of Compression as well as the allowed number of Window Exposure events. Compression Exceed onDemand uses Thin X Protocol to handle the communication between Exceed onDemand Client and Exceed onDemand Server. This connection is usually slower because it is more likely for Exceed onDemand Client to be running in a remote location, connecting to the Server over dial-up or broadband connections. One of the characteristics of TXP is its ability to compress data so fewer bits have to travel over the network connection. The compression ratio is controlled by Exceed onDemand Proxy, but users can override it under certain conditions. If the network connection is FAST, the Proxy will default the compression setting to “Large Data Only,” which means that only images and font data will be compressed. TXP commands will not be compressed. Users can override this setting to either “None” or “All Data.” The “None” setting benefits Exceed onDemand when running on a very fast network, one so fast that any performance benefit gained by decreasing the number of bits transferred is offset by the time Exceed onDemand takes to compress and decompress data. However, users will observe little bandwidth reduction with this setting. “All Data” compression, as the name implies, compresses all data. The bandwidth usage is at the minimum. Users cannot adjust the Compression setting if the connection is “Slow.” 36
Font Caching > Exceed onDemand 5 — A Technical Whitepaper Since all fonts are located on the Server and it is the Client that has to display the text on the screen, the fonts have to be transferred from the Server to the Client, and this process can be time consuming and repetitive. Font Caching can help. Caching is a mechanism that temporarily stores frequently accessed information in a location that is easier and faster to access than the original storage place. With Font Caching turned on, Exceed onDemand Client caches all requested fonts persistently in local storage. Exceed onDemand Proxy consults the Client’s font cache content first before sending the font over the network. This mechanism ensures the maximum efficiency and reduces redundant network traffic. Users can further specify the maximum number of fonts that can be stored in the cache directory. Image Caching The concept of Image Caching is similar to Font Caching; large images can take a long time to transfer from the proxy to the client. Exceed onDemand can persistently cache large images in local storage to save bandwidth and improve performance. Users can also define the image size threshold and the maximum storage size for the image cache. Figure 15 — Set the connection speed to Fast, Slow or Auto-detect OpenGL API OpenGL API is the premier environment for developing portable, interactive 2D and 3D graphics applications. Since its inception, OpenGL API has become the industry’s most widely used and supported 3D graphics application programming interface. Exceed onDemand, while promising the performance and functionality of Exceed for the mobile workforce, has harnessed the power of OpenGL API. It now supports OpenGL applications, such as scientific and data analysis, geographic mapping, content creation, CAD, CAM and CAE. 37
- Page 1: Transforming Information into Intel
- Page 4 and 5: Exceed onDemand 5 — A Technical W
- Page 6 and 7: Exceed onDemand 5 — A Technical W
- Page 8 and 9: Exceed onDemand 5 — A Technical W
- Page 10 and 11: Exceed onDemand 5 — A Technical W
- Page 12 and 13: Exceed onDemand 5 — A Technical W
- Page 14 and 15: Exceed onDemand 5 — A Technical W
- Page 16 and 17: Exceed onDemand 5 — A Technical W
- Page 18 and 19: Exceed onDemand 5 — A Technical W
- Page 20 and 21: Exceed onDemand 5 — A Technical W
- Page 22 and 23: Exceed onDemand 5 — A Technical W
- Page 24 and 25: Exceed onDemand 5 — A Technical W
- Page 26 and 27: Exceed onDemand 5 — A Technical W
- Page 28 and 29: Exceed onDemand 5 — A Technical W
- Page 30 and 31: Exceed onDemand 5 — A Technical W
- Page 32 and 33: Exceed onDemand 5 — A Technical W
- Page 34 and 35: Exceed onDemand 5 — A Technical W
- Page 38 and 39: Exceed onDemand 5 — A Technical W
- Page 40 and 41: Exceed onDemand 5 — A Technical W
- Page 42 and 43: Exceed onDemand 5 — A Technical W
- Page 44 and 45: Exceed onDemand 5 — A Technical W
- Page 46 and 47: Exceed onDemand 5 — A Technical W
- Page 48 and 49: Exceed onDemand 5 — A Technical W
- Page 50 and 51: Exceed onDemand 5 — A Technical W
- Page 52 and 53: Exceed onDemand 5 — A Technical W
- Page 54 and 55: Exceed onDemand 5 — A Technical W
- Page 56 and 57: Exceed onDemand 5 — A Technical W
- Page 58 and 59: Exceed onDemand 5 — A Technical W
- Page 60 and 61: Exceed onDemand 5 — A Technical W
- Page 62: Server > Desktop Consolidation > X
Font Caching<br />
> <strong>Exceed</strong> <strong>onDemand</strong> 5 — A <strong>Technical</strong> <strong>Whitepaper</strong><br />
Since all fonts are located on the Server and it is the Client that has to display the text on the screen, the<br />
fonts have to be transferred from the Server to the Client, and this process can be time consuming and<br />
repetitive. Font Caching can help. Caching is a mechanism that temporarily stores frequently accessed<br />
information in a location that is easier and faster to access than the original storage place. With Font<br />
Caching turned on, <strong>Exceed</strong> <strong>onDemand</strong> Client caches all requested fonts persistently in local storage.<br />
<strong>Exceed</strong> <strong>onDemand</strong> Proxy consults the Client’s font cache content first before sending the font over<br />
the network. This mechanism ensures the maximum efficiency and reduces redundant network traffic.<br />
Users can further specify the maximum number of fonts that can be stored in the cache directory.<br />
Image Caching<br />
The concept of Image Caching is similar to Font Caching; large images can take a long time to transfer<br />
from the proxy to the client. <strong>Exceed</strong> <strong>onDemand</strong> can persistently cache large images in local storage<br />
to save bandwidth and improve performance. Users can also define the image size threshold and the<br />
maximum storage size for the image cache.<br />
Figure 15 — Set the connection speed to Fast, Slow or Auto-detect<br />
OpenGL API<br />
OpenGL API is the premier environment for developing portable, interactive 2D and 3D graphics<br />
applications. Since its inception, OpenGL API has become the industry’s most widely used and<br />
supported 3D graphics application programming interface. <strong>Exceed</strong> <strong>onDemand</strong>, while promising<br />
the performance and functionality of <strong>Exceed</strong> for the mobile workforce, has harnessed the power<br />
of OpenGL API. It now supports OpenGL applications, such as scientific and data analysis,<br />
geographic mapping, content creation, CAD, CAM and CAE.<br />
37
Change language