● Establish a reliable session from the client to the server and release the session in an orderly manner.
● Agree on a common level of protocol functionality using capability negotiation.
● Exchange content between client and server using compact encoding.
● Suspend and resume the session.
● Provide HTTP 1.1 functionality.
● Exchange client and server session headers.
● Interrupt transactions in process.
● Push content from server to client in an unsynchronized manner.
● Negotiate support for multiple, simultaneous asynchronous transactions.
The core of the WSP design is a binary form of HTTP. Consequently, all methods defined by HTTP 1.1 are supported. In addition, capability negotiation can be used to agree on a set of extended request methods, so that full compatibility to HTTP applications can be retained. HTTP content headers are used to define content type, character set encoding, language, etc., in an extensible manner. However, compact binary encoding is defined for the well-known headers to reduce protocol overhead.
The life cycle of a WSP is not tied to the underlying transport protocol. A session can be
suspended while the session is idle to free up network resources or save battery power. A lightweight session re-establishment protocol allows the session to be resumed without the overload of full-blown session establishment. A session may be resumed over a different bearer network.
WSP allows extended capabilities to be negotiated between peers (as an example this allows for both high-performance, feature-full implementation as well as simple, basic, and small implementations). WSP provides an optimal mechanism for attaching header information to the acknowledgment of a transaction. It also optionally supports asynchronous requests so that a client can submit multiple requests to the server simultaneously. This improves utilization of air time and latency as the result of each request can be sent to the client when it becomes available.
Source of Information : Elsevier Wireless Networking Complete 2010
0 comments: on "WAP Architecture - Wireless Session Protocol"
Post a Comment