|
|
The following sections provide an overview of the Design Studio application and the Cisco Content Transformation Engine (CTE) 1400:
The Cisco Content Transformation Engine (CTE) 1400 Design Studio application creates transformation instructions that convert web pages into a format appropriate for devices such as the following:
Design Studio publishes transformation instructions to the Cisco CTE 1400, an appliance that handles requests for web pages from wireless devices and uses the transformation instructions to convert HTML/XML pages into wireless-compatible formats. This real-time conversion does the following:
Typically, wireless devices are constrained by display size, data input features, and download time. You can exclude and modify web page content by indicating in Design Studio how you want a web page to appear when delivered to wireless devices. Design Studio creates content transformation instructions, referred to as transformation rules, based on your decisions.
Depending on the web site you want to transform and the wireless devices you want to support, you can choose to create transformation rules for all or just a few of a web site's pages. The Cisco CTE 1400 handles web pages as noted in Table 1-1.
Table 1-1 How the Cisco CTE 1400 Handles Web Pages
|
|
1 WML = Wireless Markup Language 2 HDML = Handheld Device Markup Language |
Design Studio simplifies the task of transforming web page content as follows:
The Cisco CTE 1400 appliance uses rules uploaded from Design Studio to fulfill web page requests from wireless devices. Figure 1-1 shows the path for a wireless user request for a web page.
 |
Note The numbers in Figure 1-1 refer to the following process. |
The path the wireless user request takes is as follows:
1. A wireless user requests a URL. A wireless carrier transmits the request to a communications tower, through the Wireless Application Protocol (WAP) carrier gateway, and to the Internet.
2. The server load balancer that receives the request evaluates the request header. The server load balancer directs HTML/XML requests to the web server farm and directs requests from wireless devices to the CTE.
3. The CTE terminates the request and then, acting as a proxy, sends a request to the server load balancer for the HTML/XML page.
4. When the CTE receives the page, it uses the rules in the configuration file to transform the content.
5. The CTE sends the transformed page to the server load balancer, for forwarding to the wireless device.
The Cisco CTE 1400 and Design Studio support the formats most commonly used for web sites and wireless devices.
Web site content in the following formats is supported:
Wireless device microbrowsers do not support all content types. Thus, the Cisco CTE 1400 does not transform the following:
The Cisco CTE 1400 passes that content to a wireless device as is.
Table 1-2 lists the destination devices supported by the Cisco CTE 1400.
|
|
1 cHTML = Compact HTML 2 WML = Wireless Markup Language |
Many wireless devices are constrained by display size, navigation, and download time, as described in the following sections. Take these factors into consideration as you choose content for wireless delivery.
Web pages are typically optimized for a 800 x 600 screen resolution; they display reasonably at a 640 x 480 resolution. While some wireless devices have a 640 x 320 screen resolution, some devices have a much more limited display size. The minimum display size is approximately 5 lines of 30 characters each.
The amount of web content you select for display on a wireless device impacts the usability of the content.
A well-designed web site uses few clicks to access important content. That same design may not work well on some wireless devices; two or three clicks might be inconvenient, for example, to a cell phone user.
When the page to be served to a wireless device exceeds the amount of text that can display on the device screen, the Cisco CTE 1400 breaks up the page into chunks, serves the first chunk, waits for a request to serve the next chunk, serves the second chunk, and so on.
Large amounts of text take longer to download and require the wireless user to issue requests for the next "page" of content. Depending on the device, the user may request the continuation of a page by spinning a trackwheel, pressing a button, or tapping a More button.
Suppose your company wants to provide wireless access to technical support Case Query web pages. You might create rules in Design Studio that transform the pages as follows:
Figure 1-2 shows a sample Case Query web page and the first page of transformed content as displayed on a RIM handheld device.
Posted: Mon Aug 18 17:03:07 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
