Result notification message

If the Push Initiator requests to receive a result notification when it sends a push message to a bb device, the PPG sends a notification to the Push Initiator indicating whether the push message was delivered, was undeliverable, or expired waiting to be delivered.

Here's an example of a result notification message.

<?xml version="1.0"?>
<!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP 2.1//EN" "http://www.openmobilealliance.org/tech/DTD/pap_2.1.dtd">
<pap>
  <resultnotification-message push-id="999999999"
        sender-address="https://www.pushdatadomain/paprequestpage"
        sender-name="RIM Push-Data"
        message-state="delivered"
        code="1000"
        desc="OK">
     <address address-value="PIN00003"/>
  </resultnotification-message>
</pap>

Here's an example of a result notification repsonse from the PPG.

<?xml version="1.0"?>
 <!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP 2.1//EN"
"http://www.openmobilealliance.org/tech/DTD/pap_2.1.dtd">
<pap>
  <resultnotification-response push-id="999999999"
                 code="1000"
                 desc="OK">
		</resultnotification-response>
</pap>

If the request is so badly constructed that the PPG cannot identify the kind of request it represents, or if the version of the protocol is not supported, the PPG sends back to the Push Initiator a bad message response. The status code is either 2000, meaning a bad request, or 3002, meaning that the version is not supported. The bad message response might contain a fragment of the unrecognizable message in the bad-message-fragment attribute.

<?xml version="1.0"?>
<!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP 2.1//EN" "http://www.openmobilealliance.org/tech/DTD/pap_2.1.dtd">
<pap><badmessage-response code="2000" desc="Not understood due to malformed syntax." bad-message-fragment=""/>
</pap>