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
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
// Copyright 2026-Present Datadog, Inc.
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
/// A [`ConnectionId`] uniquely identifies a single connection managed by the
/// FFI host (e.g. a call to `rc_conn_new()`).
///
/// Invariant: guaranteed to be sequential, starting from 0 for the first
/// connection created, per client instance.
;
/// Lifecycle events for a single I/O connection brokered by the FFI host.
///
/// The lifecycle event is associated with a [`ConnectionId`] identifying the
/// underlying connection
///
/// Valid state transitions for a connection are:
///
/// ```text
/// ┌──────────────┐
/// ┌───│ Init │
/// │ └──────────────┘
/// │ │
/// │ ▼
/// │ ┌──────────────┐
/// │ │ Connected │◀──┐
/// │ └──────────────┘ │
/// │ │ │ Reconnect &
/// │ ▼ │ reuse
/// │ ┌──────────────┐ │
/// │ │ Disconnected │───┘
/// │ └──────────────┘
/// │ │
/// │ ▼
/// │ ┌──────────────┐
/// └──▶│ Release │
/// └──────────────┘
/// ```
///
/// The FFI host emits lifecycle events into this client library, and as such
/// the correctness of lifecycle transitions depends on the correctness of the
/// FFI host application.
///
/// Implementations MUST not panic if an invalid state transition is reported,
/// instead it SHOULD refuse to change state and raise an error.
///
/// Note that:
///
/// * A connection does not need to ever transition through the
/// [`Self::Connected`] state; it can start in the [`Self::Init`] state and
/// transition to the [`Self::Release`] state immediately after.
///
/// * A connection can be reused after becoming disconnected by transitioning
/// back to the [`Self::Connected`] state.
///
/// A [`ConnectionUpdate`] contains a [`ConnectionEvent`] update, and the
/// corresponding [`ConnectionId`] it applies to.