Add enhanced message and its corresponding error-handling, resent mechanism Fix #61.

[jimhorng]

Add enhanced message and its corresponding error-handling, resent mechanism Fix #61. Problem Addressed (Reference to Redth):

• Async response of error response and response time varies from 0.1 ~ 0.8 secs by observation
• Sent success do not response, which means client cannot always expect for response.
• Async close write stream connection after error-response.
• All notification sent after failed notification are discarded, the responding error-response and closing client's write connection will be delayed
• Sometimes APNS close socket connection arbitrary

Solution:

• Non-blocking ssl socket connection to send notification without waiting for response.
• A separate thread for constantly checking error-response from read connection.
• A sent notification buffer used for re-sending notification that were sent after failed notification, or arbitrary connection close by apns.
• Reference to non-blocking apns pull request by minorblend, enhanced message by hagino3000

Result:

• Send notification at throughput of 1000/secs
• In worse case of when 1st notification sent failed, error-response respond after 1 secs and 999 notification sent are discarded by APNS at the mean time, all discarded 999 notifications will be resent without loosing any of them. With the same logic, if notification resent failed, it will resent rest of resent notification after the failed one.

Test: Sample code to test above function

[djacobs]

Thanks - this is significant! I'll review shortly.

[jimhorng]

Hi djacobs, I had updated comment to include test script to test the new functionalities.

[djacobs]

@jimhorng OK - I am catching up in the wrong order, obviously. Thank you for this and for your patience.

[jimhorng]

Thanks for reviewing this PR, hope this helps :D