You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 9, 2018. It is now read-only.
Having check_for_errors enabled is a huge performance hit. Would it be possible to read errors from the socket in such a way that doesn't block further sending? You would need to keep track of the order in which notifications were sent, because in the event of a disconnect and subsequent read from the socket, the failed notification might not be the last one sent and something that was previously marked delivered might need to be changed to failed.
Having check_for_errors enabled is a huge performance hit. Would it be possible to read errors from the socket in such a way that doesn't block further sending? You would need to keep track of the order in which notifications were sent, because in the event of a disconnect and subsequent read from the socket, the failed notification might not be the last one sent and something that was previously marked delivered might need to be changed to failed.
PushSharp seems to handle this well: https://github.com/Redth/PushSharp/blob/master/PushSharp.Apple/ApplePushChannel.cs
The text was updated successfully, but these errors were encountered: