The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

Push Messaging

Windows Mobile 6.5

4/8/2010

This code sample is named FileClient. It demonstrates how to implement a push-client that receives push-messages, saves the message's body to a file, and then calls ShellExecuteEx to perform an action on the file (which can be an executable file or a document).

The Setup in a CAB code sample can be used to create a CAB file for deploying this application.

The value of the X-MS-FileName header field in the message's headers section specifies the name of the saved file.

Application parameters can be set by filling-in the X-MyCompany-Params header field.

The value of CSIDL_WINDOWS contains the name of the directory where the file is saved.

Since the message is traveling over the SMS transport, the maximum message size determines the maximum size of an application that can be pushed to a mobile device. Most Short Message Service Center's (SMSC's) limit this size to 64KB.

The Application ID of this push-client is "fileclient", To be intercepted by this push-client, a push-message must have a value of "fileclient" for the X-WAP-Application-ID header field.