apns-h2 0.11.0

Async HTTP/2 APNs client based on hyper
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64

# apns-h2

[![CI Status](https://github.com/threema-ch/apns-h2/actions/workflows/ci.yml/badge.svg)](https://github.com/threema-ch/apns-h2/actions/workflows/ci.yml)
[![MIT licensed](https://img.shields.io/badge/license-MIT-blue.svg)](./LICENSE)
[![crates.io](https://img.shields.io/crates/v/apns-h2)](https://crates.io/crates/apns-h2)
[![docs.rs](https://img.shields.io/badge/docs.rs-apns-h2-blue)](https://docs.rs/apns-h2/)

Async HTTP/2 APNs client based on hyper.

## Requirements

Needs a Tokio executor version 1.0 or later and Rust compiler version 1.88.0 or later.

## Features

* Fast asynchronous sending, based on [h2](https://github.com/carllerche/h2) and
  [hyper](https://github.com/hyperium/hyper) crates.
* Payload serialization/deserialization with
  [serde](https://github.com/serde-rs/serde).
* Provides a type-safe way of constructing different types of payloads. Custom
  data through `Serialize`, allowing use of structs or dynamic hashmaps.
* Supports `.p12` certificate databases to connect using a custom certificate.
* Supports `.p8` private keys to connect using authentication tokens.
* If using authentication tokens, handles signature renewing for Apple's guidelines
  and caching for maximum performance.
* Cryptography primitives are provided either by openssl or
  [AWS-LC](https://github.com/aws/aws-lc).

## Examples

The library supports connecting to Apple Push Notification service [either using
a
certificate](./examples/certificate_client.rs)
with a password [or a private
key](./examples/token_client.rs) with
a team id and key id. Both are available from your Apple account and with both
it is possible to send push notifications to one application.

To see it used in a real project, take a look to the [Threema Push
Relay](https://github.com/threema-ch/push-relay), which is a project by Threema
to accept and forward pushes to the appropriate push backends.

## Gotchas

We've been pushing notifications daily through this library and are quite happy
with it. Some things to know, if you're evaluating the library for production
use:

* Do not open new connections for every request. Apple will treat it as Denial of Service attack and block the sending IP address. When using the same `Client` for multiple requests, the `Client` keeps the connection alive if pushing steady traffic through it.

* For one app, one connection is quite enough already for certain kind of
  loads. With http2 protocol, the events are asynchronous and the pipeline can
  hold several outgoing requests at the same time. The biggest reason to open
  several connections is for redundancy, running your sender service on different
  machines.

* It seems to be Apple doesn't like when sending tons of notifications with
  faulty device tokens and it might lead to `ConnectionError`s. Do not send more
  notifications with tokens that return `Unregistered`, `BadDeviceToken` or
  `DeviceTokenNotForTopic`.

## Tests

`cargo test`