This kind of handshake over a cell phone would be very wasteful, and so wireless networks rely on slim protocols. TCP/IP is in fact a protocol with a very high overhead-consider for example a simple TCP handshake: A SYN packet is transmitted from the client to server, the server acknowledges with a SYN-ACK, and the client transmits its own ACK. The wireless world deals with such problems as small bandwidth and high latency, problems that for the most part the Internet doesn't get itself too concerned about.
In this case a WAP gateway translates between the IP packet world of the Internet, and a wireless phone/data network, which is a different beast all together. The first type is called a WAP gateway server, and like any gateway it is designed to translate messages between two different types of networks. Two types of servers are required to make WAP work as it is designed to. The other two parts of the WAP equation reside in the realm where Linux works best-the server environment. To view WAP pages on a Linux system I do recommend an Open Source, Java-based solution called Waplet, which is available on Sourceforge at:
#Linux logtail norwap code
As we'll see in parts two and three of this series code development for WAP is as simple as using your favorite text editor. Unfortunately, most of these IDEs were developed for Wintel systems, and those of us who prefer to use Linux as a development platform will find our IDE selections limited. Several development environments exist for the PC platform, and these include their own WAP browsers. It isn't necessary to have a WAP-enabled device to view WML pages, however. This is the web browser embedded in WAP-enabled devices, and this is the browser that renders WML and WMLScript and provides the user interface to all WAP applications. Like Internet professionals and web developers need an understanding of how the Internet and Web work, so too do WAP developers need an understanding of the underlying protocols and systems that make the wireless web work. WAP is designed to bring simple web-based functionality to cell phones and palmtops. Part I: WAP - The Wireless Web's Architecture
#Linux logtail norwap how to
To understand how this wireless web technology works, its best to see it from three distinct angles: how the architecture transmits web pages to wireless devices how you can create such a wireless web page, and how to introduce interactivity to those web pages. WAP stands for Wireless Application Protocol, and it's one way to present hypertext data to a wireless browser, like those on cellular phones or PDAs. WAP is one of the technologies being implemented to bring the web to the wireless world.