reactor
/
ptth
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
ptth/crates/ptth_quic/src/prelude.rs

58 lines
616 B
Rust
Raw Normal View History

add QUIC client
2021-07-17 01:10:30 +00:00
pub use std::{
:construction: P3 can now tell apart P2 and P4 peers
2021-07-17 07:11:34 +00:00
collections::*,
:heavy_plus_sign: add the multi-call server This exe can act as both a PTTH and PTTH_QUIC end server. It's only 17 MB, which is a big improvement over the 15 + 15 for shipping both servers as their own exes
2021-10-02 18:13:14 +00:00
ffi::OsString,
:construction: begin building PTTH_DIREC Working: - Client sends the first cookie to relay - Relay learns client's WAN address Next steps: - Associate PTTH_DIREC state with QUIC connection so we can track it / destroy it all at once - P3 asks P4 to accept PTTH_DIREC connection
2021-10-11 01:59:08 +00:00
iter::FromIterator,
:star: use udp_over_tcp for both PTTH_QUIC end server and relay server - `cargo run -p ptth_quic --bin ptth_quic_relay_server -- --tcp-listen-port 4440` - `cargo run -p ptth_quic --bin ptth_quic_end_server -- --use-udp-over-tcp true --relay-addr 127.0.0.1:4440 --server-id my_server` - `cargo run -p ptth_quic_client_gui -- --client-id me` - `nc -l -p 5900` - (Open my_server, 5900 in the client GUI) - `nc 127.0.0.1 50369` (or whatever port the GUI picked)
2022-10-31 18:50:42 +00:00
net::{
Ipv4Addr,
SocketAddr,
SocketAddrV4,
},
:loud_sound: counting active QUIC connections for P3
2021-07-17 22:03:55 +00:00
sync::{
Arc,
atomic::{
AtomicU64,
Ordering,
},
},
:construction: begin building PTTH_DIREC Working: - Client sends the first cookie to relay - Relay learns client's WAN address Next steps: - Associate PTTH_DIREC state with QUIC connection so we can track it / destroy it all at once - P3 asks P4 to accept PTTH_DIREC connection
2021-10-11 01:59:08 +00:00
time::{
Duration,
Instant,
},
add QUIC client
2021-07-17 01:10:30 +00:00
};
:recycle: refactor
2021-07-18 18:41:25 +00:00
pub use anyhow::{
Context,
bail,
};
add end server
2021-07-17 00:58:35 +00:00
pub use futures_util::StreamExt;
modify client to accept connections from a local TCP client
2021-07-17 02:39:08 +00:00
pub use tokio::{
io::{
AsyncReadExt,
AsyncWriteExt,
},
:star: use udp_over_tcp for both PTTH_QUIC end server and relay server - `cargo run -p ptth_quic --bin ptth_quic_relay_server -- --tcp-listen-port 4440` - `cargo run -p ptth_quic --bin ptth_quic_end_server -- --use-udp-over-tcp true --relay-addr 127.0.0.1:4440 --server-id my_server` - `cargo run -p ptth_quic_client_gui -- --client-id me` - `nc -l -p 5900` - (Open my_server, 5900 in the client GUI) - `nc 127.0.0.1 50369` (or whatever port the GUI picked)
2022-10-31 18:50:42 +00:00
net::{
TcpListener,
TcpSocket,
UdpSocket,
},
:construction: P3 can now tell apart P2 and P4 peers
2021-07-17 07:11:34 +00:00
sync::{
Mutex,
mpsc,
},
:construction: sketching out the request-response control protocol
2021-07-17 06:43:14 +00:00
task::JoinHandle,
modify client to accept connections from a local TCP client
2021-07-17 02:39:08 +00:00
};
:construction: begin building PTTH_DIREC Working: - Client sends the first cookie to relay - Relay learns client's WAN address Next steps: - Associate PTTH_DIREC state with QUIC connection so we can track it / destroy it all at once - P3 asks P4 to accept PTTH_DIREC connection
2021-10-11 01:59:08 +00:00
pub use rand::{
Rng,
RngCore,
};
add end server
2021-07-17 00:58:35 +00:00
pub use tracing::{
debug,
error,
info,
:mute: drop some debugs to traces
2021-07-17 21:42:51 +00:00
trace,
add end server
2021-07-17 00:58:35 +00:00
warn,
};
:recycle: refactor: start moving protocol into its own module
2021-07-18 17:57:54 +00:00
pub use crate::protocol;
add end server
2021-07-17 00:58:35 +00:00
pub use crate::quinn_utils::*;