Note that there are some explanatory texts on larger screens.

plurals
  1. POBlackBerry push client application subscription
    primarykey
    data
    text
    <p>I have few things to be clarified in BlackBerry push client applications. I have developed an push-enabled application which can receive push messages from the sample push initiator application installed on a publicly accessible location (through BIS). I have now run into a question about sending personalized messages to each device. For that matter I need to use subscription API that comes with BlackBerry push SDK. <a href="http://supportforums.blackberry.com/t5/BlackBerry-Push-Development/Confusion-in-sample-client-side-application/td-p/1776667" rel="nofollow">This question</a> is similar to what has been posted here, but it contains no information for me. My questions are,</p> <ol> <li>I used the registration API for BlackBerry client app registration to receive push messages from PPG. It requires only app-ID, device-port and push URL(not push initiator URL). Client app registers itself when the application UI starts up(this is how I register with push API). Is this all I need to do to get a subscription for that client with push initiator or does client need to contact push initiator directly for a subscription?</li> <li>Why do I need to provide subscribe/unsubscribe URLs in the push initiator application (I don't provide any unsubscribe/subscribe facility in the client push application ) or is there a way to achieve this through application manager/operating system? or do I need to get unsubscribed users from the PushResult object and process them? </li> <li>How does push initiator come to know about clients initially when there is no mechanism for the push client to subscribe with push initiator?</li> <li>Is there a blog post or tutorial describing each and every step involved in the entire communication process apart from the documentation materials provided by RIM?</li> </ol> <p>Currently I am using Push Essentials but might migrate to Push Plus service later(in the distance future).</p> <p>Kindly appreciate your quick response.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload