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

[riegie]

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]

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

[tgwizard]

This would be awesome! 👍 😄

[danshev]

+1

[dfujiwara]

+1

[agandhi4]

This project does a great job encapsulating HTTP/2 API

https://github.com/joshfriend/apns3

[djacobs]

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

[captainkirkwood]

+1

[Erfa]

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]

Any updates?