anysc-rustls 0.1.1

crate-level shim layer for any {async crate}-rustls
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
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112

<div align="center">
    <h1><code>anysc-rustls</code></h1>
    <p>crate-level shim layer for any <code>{async crate}-rustls</code></p>
</div>

<br/>

## Usage

See the next section for details.

1. Add to `dependencies`:
  
    ```toml
    [dependencies]
    # ...
    anysc-rustls = { version = "0.1", optional = true }
    ```

2. **Activate one of `io_*` feature flags**:
  
    - `io_tokio` ( `tokio::io` interface, used by:
      [`tokio`](https://github.com/tokio-rs/tokio),
      [`nio`](https://github.com/nurmohammed840/nio),
      etc. )
    - `io_futures` ( `futures-io` interface, used by:
      [`async-std`](https://github.com/async-rs/async-std),
      [`smol`](https://github.com/smol-rs/smol),
      [`glommio`](https://github.com/DataDog/glommio),
      etc. )

3. Depending on the use case, enable some inheritied features:
  
    - `aws-lc-rs`
    - `aws_lc_rs`
    - `early-data`
    - `fips`
    - `logging`
    - `ring`
    - `tls12`

4. Write your code with `anysc-rustls` as with `{tokio, futures}-rustls`.

<br/>

## What this does?

**Just reexporting** all the items of one of

- [`tokio-rustls`](https://github.com/rustls/tokio-rustls)
- [`futures-rustls`](https://github.com/rustls/futures-rustls)

based on the `io_*` feature flag selected.

The point is that **this is a crate**: it enables,
for some (maybe niche) crates that

* support multiple async runtimes over **different async IO interfaces**
  (`tokio::io`, `futures::io`)
* AND **optionally** provide [rustls](`https://github.com/rustls/rustls`)-powered TLS functionality
  behind a **feature flag** (like `tls`)

, to switch `{async crate}-rustls` dependencies **without any needless dependencies**.

### Problem

That's impossible by other way: if simply having a submodule reexporting
`tokio-rustls` and `futures-rustls` conditionally with respective feature flags (like `tokio-io`, `futures-io`),
indeed it works, but the crate's `[dependencies]` will be like

```toml
[dependencies]
tokio-rustls = { optional = true, version = ... }
futures-rustls = { optional = true, version = ... }

[features]
tokio-io = ...
futures-io = ...
tls = ...
```

Here, how we setup the features?

1. `tokio-io = if "tls" ["dep:tokio-rustls"]` + `futures-io = if "tls" ["dep:futures-tls"]`

    impossible.

2. `tls = if "tokio-io" ["dep:tokio-rustls"] else if "futures-io" ["dep:futures-tls"]`

    impossible.

3. `tls = ["dep:tokio-rustls", "dep:futures-rustls"]`

    works, but one of them must be needless.

So it's **impossible to avoid undesired dependencies** in this way.

### Solution

However, it's enabled by a **crate-level shim layer** as this crate:

```toml
[dependencies]
anysc-rustls = { version = "0.1", optional = true }

[features]
tls = ["dep:anysc-rustls"]
tokio-io = ["anysc-rustls?/io_tokio", ...]
futures-io = ["anysc-rustls?/io_futures", ...]
```

Yes, that's done by the `<crate>?/<feature>` syntax!