net.rim.pushsdk.subscription
Interface SubscriptionDAO

batchIncrementConsecutiveFailedPushCount(List<SubscriberPartial> subscribers)Deprecated.As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is
received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves
by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this
count because the public/BIS PPG will be implementing this logic on the platform side instead. For
enterprise/BES the push initiator must implement the logic if desired.

void

batchResetConsecutiveFailedPushCount(List<SubscriberPartial> subscribers)Deprecated.As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is
received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves
by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this
count because the public/BIS PPG will be implementing this logic on the platform side instead. For
enterprise/BES the push initiator must implement the logic if desired.

getConsecutiveFailedPushCount(SubscriberPartial subscriber)Deprecated.As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is
received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves
by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this
count because the public/BIS PPG will be implementing this logic on the platform side instead. For
enterprise/BES the push initiator must implement the logic if desired.

incrementConsecutiveFailedPushCount(String pushApplicationId,
String subscriberId)Deprecated.As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is
received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves
by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this
count because the public/BIS PPG will be implementing this logic on the platform side instead. For
enterprise/BES the push initiator must implement the logic if desired.

loadFromCache(String pushApplicationId,
String subscriberId)
Attempts to load a partial subscriber from the cache or from memory (for in-memory implementations).

void

resetConsecutiveFailedPushCount(String pushApplicationId,
String subscriberId)Deprecated.As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is
received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves
by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this
count because the public/BIS PPG will be implementing this logic on the platform side instead. For
enterprise/BES the push initiator must implement the logic if desired.

findByAppId

Finds a list of subscribers with the specified push application id. Note: Index arguments are present to address memory
concerns, since if we retrieve a full list it might be quite large. Indexes are inclusive and start at 0.

findByAppIdAndStatus

Finds a list of subscribers with the specified push application id and status. Note: Index arguments are present to address
memory concerns, since if we retrieve a full list it might be quite large. Indexes are inclusive and start at 0.

findByAppIdAndIdsAndStatus

Finds a list of subscribers for the given push application id that are in the specified subscriber id list with the
specified status. (e.g. find all subscribers that match the ids in the passed in list that for the given push application
are active)

Parameters:

pushApplicationId - the id of the push application

subscriberIds - only subscribers with one of these ids will be returned

status - only subscribers that match this status will be returned

Returns:

a list of subscribers, if found; otherwise, an empty list

Throws:

org.springframework.dao.DataAccessException - if any errors occur

findByAppIdAndType

Finds a list of subscribers with the specified push application id and type. Note: Index arguments are present to address
memory concerns, since if we retrieve a full list it might be quite large. Indexes are inclusive and start at 0.

Finds a list of subscribers with the specified push application id, type, and status. Note: Index arguments are present to
address memory concerns, since if we retrieve a full list it might be quite large. Indexes are inclusive and start at 0.

incrementConsecutiveFailedPushCount

Deprecated.As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is
received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves
by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this
count because the public/BIS PPG will be implementing this logic on the platform side instead. For
enterprise/BES the push initiator must implement the logic if desired.

Increments the count of consecutive failed push counts for a subscriber by 1.

Parameters:

pushApplicationId - the id of the push application

subscriberId - the id of the subscriber

Throws:

org.springframework.dao.DataAccessException - if any errors occur

resetConsecutiveFailedPushCount

Deprecated.As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is
received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves
by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this
count because the public/BIS PPG will be implementing this logic on the platform side instead. For
enterprise/BES the push initiator must implement the logic if desired.

Resets the count of consecutive failed push counts for a subscriber back to 0.

Parameters:

pushApplicationId - the id of the push application

subscriberId - the id of the subscriber

Throws:

org.springframework.dao.DataAccessException - if any errors occur

batchIncrementConsecutiveFailedPushCount

Deprecated.As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is
received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves
by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this
count because the public/BIS PPG will be implementing this logic on the platform side instead. For
enterprise/BES the push initiator must implement the logic if desired.

Batch increments the count of consecutive failed push counts for subscribers by 1.

Parameters:

subscribers - list of subscribers to increment count

Throws:

org.springframework.dao.DataAccessException - if any errors occur

batchResetConsecutiveFailedPushCount

Deprecated.As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is
received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves
by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this
count because the public/BIS PPG will be implementing this logic on the platform side instead. For
enterprise/BES the push initiator must implement the logic if desired.

Batch resets the count of consecutive failed push counts for subscribers back to 0.

Parameters:

subscribers - list of subscribers to reset count

Throws:

org.springframework.dao.DataAccessException - if any errors occur

getConsecutiveFailedPushCount

Deprecated.As of release 1.1, the SDK will no longer keep a count of consecutive failed pushes when result notification is
received from the PPG. If this functionality is desired it should be implemented by push initiator's themselves
by subclassing the FailureNotificationListener from the acknowledgement component. The SDK no longer keeps this
count because the public/BIS PPG will be implementing this logic on the platform side instead. For
enterprise/BES the push initiator must implement the logic if desired.

loadFromCache

Attempts to load a partial subscriber from the cache or from memory (for in-memory implementations). Returns null if the
partial subscriber could not be found in the cache or if no cache is being used.