Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Strategies & Market Trends : Gorilla and King Portfolio Candidates -- Ignore unavailable to you. Want to Upgrade?

To: Dinesh who wrote (23803)	4/28/2000 1:58:00 PM
From: John Stichnoth	Respond to of 54805

Dinesh, You are absolutely right. WAP is all of those things, and it does need to keep up with other developments. (I was thinking in terms of a previous response, which left my focus too narrow, and that part of my response wrong). Thanks for the correction. This does seem to be my day for revisiting the WAP Forum FAQ's. They address your question ("Why can't someone use TCPIP to communicate with a wireless device ?"). begin snip------------- Why isn't WAP using existing Internet standards? WAP is using existing Internet standards. The WAP architecture was designed to enable standard off-the-shelf Internet servers to provide services to wireless devices. In addition, when communicating with wireless devices, WAP uses many Internet standards such as XML, UDP and IP. The WAP wireless protocols are based on Internet standards such as HTTP and TLS but have been optimised for the unique constraints of the wireless environment. Internet standards such as HTML, HTTP, TLS and TCP are inefficient over mobile networks, requiring large amounts of mainly text based data to be sent. Standard HTML web content generally cannot be displayed in an effective way on the small size screens of pocket-sized mobile phones and pagers, and navigation around and between screens is not easy in one-handed mode. HTTP and TCP are not optimised for the intermittent coverage, long latencies and limited bandwidth associated with wireless networks. HTTP sends its headers and commands in an inefficient text format instead of compressed binary. Wireless services using these protocols are often slow, costly and difficult to use. The TLS security standard requires many messages to be exchanged between client and server which, with wireless transmission latencies, results in a very slow response for the user. WAP has been optimised to solve all these problems, utilising binary transmission for greater compression of data, and is optimised for long latency and low to medium bandwidth. WAP sessions cope with intermittent coverage and can operate over a wide variety of wireless transports using IP where possible and other optimised protocols where IP is impossible. The WML language used for WAP content makes optimum use of small screens and allows easy navigation with one hand without a full keyboard, and has built-in scalability from two-line text displays through to the full graphic screens on smart phones and communicators. --------------- It sounds like you can use TCP for wireless. At this point WTP, etc. just works a little better. Best, John