Marcel Märtens 91d296cda1 Fixed bug in tcp protocol.rs ...

- It was possible for a end_receiver to be triggered in the moment while a frame was started by not finished.
   This removed bytes from the stream with them getting lost. this almost ever was followed by a RAW frame as the TCP stream was now invalid.
   The TCP stream was then detected by participant or caused one or multiple failures
 - introduces some simplifications, removed a macro, reuse code

2020-08-24 16:22:06 +02:00

..

api.rs

using Locks a more sensitive way.

2020-08-23 21:43:17 +02:00

channel.rs

workaround for impossible RAW msg

2020-08-22 01:09:07 +02:00

lib.rs

fix master / update toolchain to 2020-08-15

2020-08-17 10:28:09 +02:00

message.rs

(See sharp/lod-history) LOD, shadows, greedy meshing, new lighting, perf

2020-08-20 20:34:59 +02:00

metrics.rs

remove some trace! in network which a) was only spam and b) could be replaced by a metric way better.

2020-08-21 18:00:14 +02:00

participant.rs

Fixed bug in tcp protocol.rs

2020-08-24 16:22:06 +02:00

prios.rs

remove some trace! in network which a) was only spam and b) could be replaced by a metric way better.

2020-08-21 18:00:14 +02:00

protocols.rs

Fixed bug in tcp protocol.rs

2020-08-24 16:22:06 +02:00

scheduler.rs

using Locks a more sensitive way.

2020-08-23 21:43:17 +02:00

types.rs

Fixed bug in tcp protocol.rs

2020-08-24 16:22:06 +02:00