Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
4/8/2010

Wireless Session Protocol (WSP) defines the methods that client and server applications use to exchange content, such as provisioning files. The methods that WSP defines include procedures for establishing and releasing sessions, the level of protocol functionality, content exchange with compact encoding, and procedures for suspending and resuming sessions. WSP uses Hypertext Transfer Protocol (HTTP) 1.1 functionality. For more detailed information about WSP, see the WAP Wireless Session Protocol Specification (OMA-WAP-TS-WSP-V1_0-20020920-C), available from this OMA Web site .

The following table shows the features that are required by the Push Router, such as connectionless unsecure push features. It does not list all of the WSP features that guided Windows Mobile development.

WSP feature Description

WSP_CL_C001 Push Protocol Data Unit (PDU) for Push Messages

The Push Protocol Data Unit (PDU) is used for sending messages without receipt confirmation from the device, as described in "Service Primitives" and "Push and Confirmed Push Facilities" in the WAP Wireless Session Protocol Specification.

WSP_CL_C002 Default Header Encoding Page

Default header encoding pages are implemented as described in "Header Encoding" in the WAP Wireless Session Protocol Specification. The SECand MACparameter assigned numbers — used by content-type — from the WAP WSP 2.0 specification are also valid.

Note:
Windows phone and Windows Mobile Professional support only the token text encoded macattribute. Windows Mobile Professional does not support the quoted text encoded macattribute.

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.