PushRouter_RegisterClient

4/8/2010

This function registers a push router client with the push router registration table.

Syntax

HRESULT PushRouter_RegisterClient(
  LPCTSTR szContentType,
  LPCTSTR szAppId,
  LPCTSTR szPath,
  LPCTSTR szParams
);

Parameters

• szContentType
  [in] Pointer to the content type of the messages routed to the push router client. The type is designated in a message header that identifies the push router client in the push router registration table.

  Note

  For details about the Content-Type header, refer to WAP Specification "WAP-251-PushMessage-20010322-a.pdf" at this OMA Web site.

• szAppId
  [in] Pointer to the push application ID of the push router client. The ID is designated in a message header that identifies the push router client in the push router registration table.

  Note

  For details about the Push Application ID, refer to WAP Specification "WAP-251-PushMessage-20010322-a.pdf" at this OMA Web site.

• szPath
  [in] Pointer to the push router client's executable file path.

• szParams
  [in] Pointer to command line parameters passed to the push router client.

Return Value

Returns S_OK if successful. If the function is unsuccessful, it can return a standard Windows HRESULT value or one of the push router-specific HRESULT values shown in the following table.

Remarks

For your push router client to receive WAP push messages, you must register it with the push router registration table by using the PushRouter_RegisterClient** function.**

During registration, the push router client must specify the types of routing entries it will be using: the push router client's content type, its push application ID, or both. The client makes one registration call per registration type. In other words, it makes one call for the content type, one call for the application ID, or one call for a combination of content type and application ID (three calls in all).

If your application is a trusted application, and another application is already registered with the same content type or application ID, the new registration will overwrite the old one.

Message routing priority is given to push router clients that register both content type and application ID. If the Content-Type and AppID headers do not agree, the push router will route the message based on the AppID header.

Requirements

See Also

Reference

PushRouter_UnRegisterClient