Symbian Developer Library


[Index] [Glossary] [Previous] [Next]

WAP Stack Overview


Provides access to a WAP 1.1 protocol stack. Applications can access WSP, WTP, and WDP through this API.

Much of the detail of this API is determined by the WAP 1.1 specifications available at, with which users of this API should be familiar.


Architectural relationships

The WAP Stack uses the client/server framework. A single server provides WAP services which applications access through a client API. Note: to avoid confusion, the component that provides WAP services is always referred to as the EPOC WAP server. WAP server by itself refers to a remote server providing WAP content.

The lowest level of the WAP protocol stack, the bearers, are implemented as plug-ins. SMS and IP are the standard bearers. There is no direct API to bearers.

The WAP Stack API is used by the WAP Engine sub-system. The WAP Engine API is suitable for applications that want to manipulate WAP content at the document and application engine level, rather than use the lower-level protocols.



The API has five key concepts: EPOC WAP server, sub-session base class, WSP, and WDP.

EPOC WAP server

The EPOC WAP server manages client access to WAP services.

The client interface to the EPOC WAP server is provided by RWAPServ.

Sub-session base class

The sub-session base class defines operations available on connections in all of WSP, WTP, and WDP.

The sub-session base class is provided by RWAPConn.


WSP (Wireless Session Protocol) is the upper-level application layer of the WAP communications stack.

Connection-orientated WSP is provided by RWSPCOConn. Supporting classes are CCapCodec, for capability negotiation, and RWSPCOTrans, which encapsulates an individual transaction.

Connectionless WSP is provided by RWSPCLConn.


WDP (Wireless Datagram Protocol) provides a general datagram transport service above the various data capable bearer services.

WDP is provided by RWDPConn.


See also

Client/Server Overview