Skip to content
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

Question - blocking behavior of getExpiredTokens() #12

Closed
flozano opened this issue Nov 9, 2013 · 2 comments
Closed

Question - blocking behavior of getExpiredTokens() #12

flozano opened this issue Nov 9, 2013 · 2 comments
Labels

Comments

@flozano
Copy link

flozano commented Nov 9, 2013

A question about getExpiredTokens:

I see in the implementation that it opens a channel and wait for it to be closed (and, in the nio eventloopgroup threads, keep reading feedback entries and add them to expiredTokens).

However, I have seen sometimes APNS feedback service not closing the socket and leaving it open until there is some feedback to write, and only then close it (I had to add a read-timeout to java-apns library because of that).

How will pushy behave if that happens?

@jchambers
Copy link
Owner

Well, it looks like we'll just hang if that happens, but the "leave connection open until feedback is available" thing is new to me. Still, we should probably add a timeout to be safe.

@jchambers
Copy link
Owner

Opened a separate issue (see #15) for the actual timeout implementation. Closing this one as the question has technically been answered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants