Routing Messages for Mobile Operators
After the Security Module processes the message, it sends the message back to the Push Router, and the Push Router checks whether the message's AppID or Content-Type header, or both AppID and Content-Type headers, are listed in the open handle table. If the AppID or Content-Type header of the associated message is not listed in the open handle table, the Push Router searches for the matching AppID or Content-Type header in the registration table.
The type of header information in the message determines routing priority. Top priority is given to client applications registered as both a Content-Type and an AppID. If the Content-Type header and the AppID header conflict, the Push Router will route the message based on the AppID header.
The following is the format for an AppID header:
X-WAP-Application-Id: [Application Identifier]
Any of the following X-WAP-Application-Id and Content-Type headers require the Push Router to direct the message to Configuration Manager — a client application of the Push Router.
The following is an example of the Configuration Manager AppID header:
x-wap-microsoft:cfgmgr.ua
The following table contains examples of the Content-Type header format that is used to route messages to Configuration Manager.
| Content-Type headers | Message content |
|---|---|
| Content-Type: application/vnd.wap.connectivity-wbxml | Compressed |
| Content-Type: text/vnd.wap.connectivity-xml | Uncompressed |
See Also
Send feedback on this topic to the authors.
© 2005 Microsoft Corporation. All rights reserved.