top | item 11249373

Push notifications from Go with Apple's new HTTP/2 protocol

134 points| geordidearns | 10 years ago |github.com | reply

18 comments

order
[+] NightMKoder|10 years ago|reply
There are few protocols that were truly worse than Apple's non-HTTP APNS protocol. You can read more at https://developer.apple.com/library/ios/documentation/Networ... , but suffice to say, the best part lies in:

If you send a notification that is accepted by APNs, nothing is returned.

If you send a notification that is malformed or otherwise unintelligible, APNs returns an error-response packet and closes the connection.

"Unintelligible" here includes of course invalid tokens, e.g. when the user uninstalls your app.

One of the upgrades was actually returning the last notification that made it through before closing the connection. Before that all you could do was add a sleep() and pray.

[+] sudhirj|10 years ago|reply
I can see that this is a library to send Push Notifications via Apple's servers, but what does it have to do with HTTP/2? Did Apple make a new version of the notifications API that uses HTTP/2? Why wouldn't they just silently upgrade the transfer protocol on the existing service?
[+] zwily|10 years ago|reply
The previous APNS service doesn't use HTTP at all.
[+] eddieroger|10 years ago|reply
Wow, that title. What this actually links to is a Go wrapper for Apple's new APNS interface, which utilizes HTTP/2. While this looks like a useful tool for the toolbelt, I would have much rather read something about how Apple got to the new protocol, or an interesting blog post about experiences using it. Having come from a shop that worked on the older protocols and been the tiniest part of an implementation with one of the brightest developers I've ever met, this new protocol is brilliant and a huge improvement, and it's a shame that this post, despite the title, doesn't do that justice.
[+] gary4gar|10 years ago|reply
How is this different from https://github.com/RobotsAndPencils/buford?
[+] edgurgel|10 years ago|reply
APNS2 has a simpler interface and doesn't do things like generate website packages etc. APNS2 has better test coverage, and handles errors in a more go-like way. (Returns a response if a documented response was received from Apple, or an error where an unexpected error occurs.)

We are running this in production at http://carnival.io to send millions of notifications, to my knowledge buford has not been tested in production yet.

[+] Hbthegreat|10 years ago|reply
Can't wait for people to start saying APNS like they say "sequel" for SQL. It is going to make for some hilarious standups.
[+] pvdebbe|10 years ago|reply
'appens or a-pens?
[+] deejbee|10 years ago|reply
I only read the title and just thought... so Apple 'invented' their own HTTP/2 protocol now. that really wouldn't surprise me. one. little. bit.
[+] dao-|10 years ago|reply
It would have surprised me but it also isn't something I would absolutely rule out a priori :)

Also, it's a pretty bad headline from what I (non-native speaker) can tell. You have a point, not quite sure why you're being downvoted.