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
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
//! Server-side Bevy types and items for networking.
//!
//! Note that this crate itself does not provide any logic for using transports
//! i.e. polling, connecting, or writing. This module simply provides the items
//! so that other crates can build on top of them, allowing interoperability.
use ;
use *;
use Derivative;
use crateDisconnectReason;
use ;
/// System set for server-side networking systems.
/// A [`Condition`]-satisfying system that returns `true` if the server `T`
/// exists *and* is in the [`Open`] state.
///
/// # Example
///
/// ```
/// # use bevy_app::prelude::*;
/// # use bevy_ecs::prelude::*;
/// # use aeronet::server::{ServerTransport, server_open};
/// # fn run<T: ServerTransport + Resource>() {
/// let mut app = App::new();
/// app.add_systems(Update, my_system::<T>.run_if(server_open::<T>));
///
/// fn my_system<T: ServerTransport + Resource>(server: Res<T>) {
/// // ..
/// }
/// # }
/// ```
///
/// [`Condition`]: bevy_ecs::schedule::Condition
/// [`Open`]: crate::server::ServerState::Open
/// A [`Condition`]-satisfying system that returns `true` if the server `T`
/// exists *and* is in the [`Closed`] state.
///
/// # Example
///
/// ```
/// # use bevy_app::prelude::*;
/// # use bevy_ecs::prelude::*;
/// # use aeronet::server::{ServerTransport, server_closed};
/// # fn run<T: ServerTransport + Resource>() {
/// let mut app = App::new();
/// app.add_systems(Update, my_system::<T>.run_if(server_closed::<T>));
///
/// fn my_system<T: ServerTransport + Resource>(server: Res<T>) {
/// // ..
/// }
/// # }
/// ```
///
/// [`Condition`]: bevy_ecs::schedule::Condition
/// [`Closed`]: crate::server::ServerState::Closed
/// The server has completed setup and is ready to accept client
/// connections, changing state to [`ServerState::Open`].
///
/// See [`ServerEvent::Opened`].
///
/// [`ServerState::Open`]: crate::server::ServerState::Open
/// [`ServerEvent::Opened`]: super::ServerEvent::Opened
/// The server can no longer handle client connections, changing state to
/// [`ServerState::Closed`].
///
/// See [`ServerEvent::Closed`].
///
/// [`ServerState::Closed`]: crate::server::ServerState::Closed
/// [`ServerEvent::Closed`]: super::ServerEvent::Closed
/// A remote client has requested to connect to this server.
///
/// The client has been given a key, and the server is trying to establish
/// communication with this client, but messages cannot be transported yet.
///
/// For a given client, the transport is guaranteed to emit this event
/// before [`ServerEvent::Connected`].
///
/// See [`ServerEvent::Connecting`].
///
/// [`ServerEvent::Connecting`]: super::ServerEvent::Connecting
/// [`ServerEvent::Connected`]: super::ServerEvent::Connected
/// [`ServerEvent::Disconnected`]: super::ServerEvent::Disconnected
/// A remote client has fully established a connection to this server,
/// changing the client's state to [`ClientState::Connected`].
///
/// After this event, you can start sending messages to and receiving
/// messages from the client.
///
/// See [`ServerEvent::Connected`].
///
/// [`ClientState::Connected`]: crate::client::ClientState::Connected
/// [`ServerEvent::Connected`]: super::ServerEvent::Connected
/// A remote client has unrecoverably lost connection from this server.
///
/// This is emitted for *any* reason that the client may be disconnected,
/// including user code calling [`ServerTransport::disconnect`], therefore
/// this may be used as a signal to tear down the client's state.
///
/// See [`ServerEvent::Disconnected`].
///
/// [`ServerEvent::Disconnected`]: super::ServerEvent::Disconnected
/// A client acknowledged that they have fully received a message sent by
/// us.
///
/// See [`ServerEvent::Ack`].
///
/// [`ServerEvent::Ack`]: super::ServerEvent::Ack
/// Our server believes that an unreliable message sent to a client has probably
/// been lost in transit.
///
/// An implementation is allowed to not emit this event if it is not able to.
///
/// See [`ServerEvent::Nack`].
///
/// [`ServerEvent::Nack`]: super::ServerEvent::Nack