Wireless Application Protocol

Here's what happens when you access a Web site using a WAP-enabled device:

• 
  
  You turn on the device and open the minibrowser.
  
• 
  
  The device sends out a radio signal, searching for service.
  
• A connection is made with your service provider.
  
• You select a Web site that you wish to view.
  
• A request is sent to a gateway server using WAP.
  
• The gateway server retrieves the information via HTTP from the Web site.
  
• The gateway server encodes the HTTP data as WML.
  
• The WML-encoded data is sent to your device.
  
• You see the wireless Internet version of the Web page you selected.
  

To create wireless Internet content, a Web site creates special text-only or low-graphics versions of the site. The data is sent in HTTP form by a Web server to a WAP gateway. This system includes the WAP encoder, script compiler and protocol adapters to convert the HTTP information to WML. The gateway then sends the converted data to the WAP client on your wireless device.

What happens between the gateway and the client relies on features of different parts of the WAP protocol stack. Let's take a look at each part of the stack:

WAP protocol stack