-
Notifications
You must be signed in to change notification settings - Fork 374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
APNS to support error-response handling(enhanced message) and re-send mechanism for performance #61
Comments
I'm using PyAPNs to send 1,000,000 devices/day. And my workarounds are
Then my idea is 2 phase (1) Add error handling methods for manual use
We can check error-respose any time. (2) Provide automatic error handling mode
|
jimhorng
added a commit
to jimhorng/PyAPNs
that referenced
this issue
Jun 4, 2014
@jimhorng - do you want to make a pull request? |
djacobs
added a commit
that referenced
this issue
Jun 23, 2014
Add enhanced message and its corresponding error-handling, resent mechanism Fix #61.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem of current APNS error-response are: (reference: the problem, official doc -> The Binary Interface and Notification Format)
From my experiment of getting error-response with enhanced message format:
however, it's not guarantee 100% to get error-response for every failed notification, the network connection might also be a factor of delayed time.
Possible Solution
The solution suggested in the problem is to save sent notification in a queue with no timeout(or minimum), when error-response caught, pop out messages before the error one in queue (considered successfully sent), and re-sent others.
Which will not have performance concern if waiting for error-response in fixed time for each message sent, and also prevent error-response uncaught.
The text was updated successfully, but these errors were encountered: