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

Migrating to the new APNs Provider API based on the HTTP/2 network protocol #155

Open
riegie opened this issue Dec 22, 2015 · 9 comments
Open
Assignees

Comments

@riegie
Copy link
Contributor

riegie commented Dec 22, 2015

Is there any interest to gradually migrate this project over to the new API? Apple is recommending developers should migrate their remote notification provider servers to the more capable and more efficient HTTP/2-based API described in APNs Provider API.

https://developer.apple.com/library/ios/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Chapters/APNsProviderAPI.html#//apple_ref/doc/uid/TP40008194-CH101-SW1

Or should this project use the binary API for legacy reasons?

@djacobs
Copy link
Owner

djacobs commented Jan 15, 2016

@riegie we do want to migrate to the new API! But we've not done this yet, obviously.

@tgwizard
Copy link

This would be awesome! 👍 😄

@djacobs djacobs self-assigned this Mar 10, 2016
@danshev
Copy link

danshev commented Mar 17, 2016

+1

1 similar comment
@dfujiwara
Copy link

+1

@agandhi4
Copy link

This project does a great job encapsulating HTTP/2 API

https://github.com/joshfriend/apns3

@djacobs
Copy link
Owner

djacobs commented Jul 4, 2016

https://pypi.io/project/apns2/#description This one looks good to me as well.

@captainkirkwood
Copy link

+1

@Erfa
Copy link

Erfa commented Nov 16, 2016

I'm not sure it's smart to change this project to use the new API. Not everyone can use the new API, because HTTP/2 support is far from everywhere yet. If possible, I think it is better to create a new project that calls the new API, and make it backwards compatible with this one. This will make upgrading easy, while those who have to stay on this version for legacy reasons can do so.

@igor-semenov
Copy link

Any updates?

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

No branches or pull requests

9 participants