Prove RUDP response resend across runtimes
This commit is contained in:
parent
6040efb213
commit
4209bbb9b6
5 changed files with 161 additions and 47 deletions
|
|
@ -177,10 +177,9 @@ Current progress:
|
|||
exchange reliable ordered `schema` frames through the shared handshake and
|
||||
packet language.
|
||||
- The same harness now proves reliable ordered `schema` delivery survives one
|
||||
dropped client data packet when TypeScript sends through RUDP to C#, Kotlin,
|
||||
Python, and Rust. The drop happens below the transport connection through a
|
||||
UDP bridge, so the recovery is RUDP resend/ack behavior, not application-level
|
||||
retry.
|
||||
dropped data packet in both directions between TypeScript and C#/Kotlin/Python/Rust.
|
||||
The drops happen below the transport connection through a UDP bridge, so the
|
||||
recovery is RUDP resend/ack behavior, not application-level retry.
|
||||
- The remaining parity work is to deepen Python's server-side use of its port
|
||||
and move each runtime's existing TCP/LiteNetLib/WebSocket bodies behind those
|
||||
ports, then broaden RUDP interop into the full loss, reordering,
|
||||
|
|
|
|||
Loading…
Reference in a new issue