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
// Copyright 2026 Anapaya Systems
//
// 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.
//! The client connection ingress: the inbound packet loop.
//!
//! This is the client's single-connection analog of the server endpoint's recv
//! loop. The server's [`QuicScionConnDriver`](crate::quic::connection::QuicScionConnDriver)
//! only writes packets and drives timers — its inbound packets are read and
//! demultiplexed by the endpoint, which feeds them in with `conn.inner.recv(..)`
//! then [`ConnectionHandle::notify`]. A client owns its whole socket and has
//! exactly one connection, so there is no demultiplexing to do: this loop reads
//! datagrams and feeds them through that same seam, while the unmodified
//! `QuicScionConnDriver` handles the write side.
//!
//! It runs alongside the driver on the bootstrap task (see
//! [`connect`](super::connect)); when the connection closes, the driver returns
//! and the ingress loop is cancelled.
use Arc;
use crate::;
/// Reads inbound datagrams from `socket` and feeds them into the connection,
/// waking the driver after each one.
///
/// Returns when the socket errors or the connection has closed.
pub async