CHAPTER 1 The big picture Internet Wireless network
CHAPTER 1 The big picture Internet Wireless network WAP device WAP device WAP device WAP device WAP device WAP device Web site Web site Gateway This side knows WAP protocols This side knows TCP/IP and HTTP Converts: WAP requests to HTTP requests HTTP response to WAP response Figure 1.4 Connecting the WAP device to the Web requests from a WAP device with this model; it simply needs to format the responses to conform to the capabilities of the device. Today, the resources available for the WAP device are very limited: The display is extremely small and its drawing capabilities range from basic to nonexistent. While HTML applications are normally designed for clients running at least 800 x 600 in 256 or more colors, WAP applications are normally designed to show only a few characters in a row, and only a small number of rows on the same display. Compared to the Internet, the network connection is slow but improving, especially in Europe and Asia, which means that the application utilizes the fewest connections possible during a user s session. Processing power and memory are minimal. Based on these limitations, it is easy to imagine why WAP devices cannot support full-fledged HTML. What they do support is an XML dialect known as Wireless Markup Language (WML) and WMLScript, JavaScript s counterpart that supports a limited JavaScript subset feasible for weak phone processors. Thus, any content we return to a WAP request must be in WML, instead of in standard HTML.
Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost JSP Web Hosting services