(on company time)
|
200c07da2f
|
🚧 wip: finding a bug. It's in the udp_over_tcp code
When a TCP client disconnects, the rx loop gets confused and goes into an
infinite loop without ever yielding.
|
2022-12-20 14:40:51 -06:00 |
|
(on company time)
|
74fb0cbe5a
|
🐛 bug: patch UDP-over-TCP example
|
2022-12-19 16:36:38 -06:00 |
|
(on company time)
|
3f4bce85a4
|
✅ UDP-over-TCP passes okay
Next step is updating the relay and making sure it integrates into (our thing that uses PTTH_QUIC)
|
2022-12-19 16:25:50 -06:00 |
|
(on company time)
|
f9e10e0f64
|
⭐ 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 13:50:42 -05:00 |
|
(on company time)
|
8a302f3049
|
👕 refactor: use full address for udp_over_tcp client instead of just port
|
2022-10-31 13:15:23 -05:00 |
|
(on company time)
|
fd3c85fccd
|
⭐ add udp_over_tcp server to PTTH_QUIC relay server
maybe it'll work
|
2022-10-31 13:11:31 -05:00 |
|
(on company time)
|
b5be7709a3
|
👕 refactor: extract configs for client and server
|
2022-10-31 11:36:03 -05:00 |
|
(on company time)
|
edd7e8de54
|
⭐ proof of concept for UDP-over-TCP
|
2022-10-31 11:24:15 -05:00 |