Marcel Märtens 383482a36e Quic: We had the followuing problem: ... - locally we open a stream, our local Drain is sending OpenStream - remote Sink will know this and notify remote Drain - remote side sends a message - local sink does not know about the Stream. as there is (and CANT) be a wat to notify local Sink from local Drain (it could introduce race conditions). One of the possible solutions was, that the remote drain will copy the OpenStream Msg ON the Quic::stream before first data is send. This would work but is complicated. Instead we now just mark such streams as "potentially open" and we listen for the first DataHeader to get it's SID. add support for unreliable messages in quic protocol, benchmarks		2021-04-29 15:58:23 +02:00
..
benches	network scheduler and rawmsg cleanup	2021-03-26 08:57:42 +01:00
examples	change some Ordering::Relaxed to Ordering::SeqCst when we do not want to have it moved/or taken effects from other threads.	2021-04-07 23:17:09 +02:00
protocol	Quic: We had the followuing problem:	2021-04-29 15:58:23 +02:00
src	Quic: We had the followuing problem:	2021-04-29 15:58:23 +02:00
tests	Change the way Network is dropped.	2021-03-03 11:28:40 +01:00
Cargo.toml	Quic: We had the followuing problem:	2021-04-29 15:58:23 +02:00