Albin Corén
Albin Corén
This also allows for some refactoring to lessen code reuse by calling this method instead of duplicating the check everywhere.
I could do publish it on NuGet, will update if/once I do. As for production ready, I have had it in production on 5+ projects.
What is the purpose of this exactly? To delay the running of connection.Update() to the end of the frame?
All API's in Ruffles are 100% thread safe and many are threaded under the hood already.
Good catch, thanks! The design is meant to roll over. I will work on fixing this.
Happened to me on Linux when the tmp storage device was full.
Whats wrong with NuGet? But sure, I have nothing against adding UPM support.
This actually requires quite a bit of changes into Ruffles since Channels are usually not aware of any reads. This addition will probably have an impact scaling aswell
Two things not yet finished: 1. IV and Counter has to be reset for every packet. Otherwise we will get a keystream mismatch when a packet goes out of order...
Counter synchronization is now implemeneted. You can have anywhere between 64-128 blocks of loss or reordering before things break. This could be massively improved by using some of the first...