The Wireless Internet Explained

Eventually there will be many applications that are particularly suited for wireless access. Designing them to take advantage of the strengths of typical mobile technologies will be an important factor. But to get started we need to look at how existing applications can be made to operate with a wireless infrastructure. Intuitively, we might think that there is one ideal way to tailor the applications so that they can be used in a mobile environment.
In actuality, after some examination, we see that there are actually many different options, including those shown in the following chart.
| Client-side | Server-side | Both |
|---|---|---|
| Native | Web | SMS |
| Enhanced | WAP | Proprietary |
| Terminal services |
Most applications will actually work over wireless links. Unless they are very sensitive to latency, require very high bandwidth, or implement poor error recovery, they should work over both circuit-switched connections and packet data networks. The applications are unaware of the network that lies underneath them. However, it is important to realize that the response time might be slow and the connections unreliable.
The option is the simplest to implement but it is also the least appealing to users with most current wireless networks. It does work satisfactorily over wireless LANs and will eventually be acceptable over 3G networks.
The most notable problems with native mode are the poor performance of the network and possible security issues when operating over public networks. It is possible to impose an additional...