Danilo Bargen

Implement benchmarks

1

- [x] Encrypt with KeyStore - [x] Encrypt with SharedKeyStore

64 bit integers are now wrapped with the [int64-buffer](https://github.com/kawanet/int64-buffer) library. To try it yourself: ```js const data = new Uint8Array([ 131, 164, 116, 121, 112, 101, 166, 117, 112, 100,...

64 bit integer handling

1

JS only has 53 bit precision integers. To be able to handle 64 bit precision integers, use the `int64` option for msgpack-lite and require `int64-buffer` as peer dependency. https://github.com/kawanet/msgpack-lite https://github.com/kawanet/int64-buffer

Go through spec and make sure that everything is implemented correctly.

Store sent messages

6

...so that when logging a send-error message, we actually know which message was lost.

We could support keeping the ws connection open after a send-error message to wait for a reconnect.

Some functionality like this. - Signaling.encryptHandshakeDataForServer(...) - Signaling.encryptHandshakeDataForPeer(...) ...could be moved into the `Peer` class. Then polymorphism could replace if-else statements.

Move from tokio-core to tokio. See also: https://github.com/tokio-rs/tokio/issues/138

Use smallvec

1

In many cases (e.g. list of tasks) we can make use of the [smallvec](https://github.com/servo/rust-smallvec) library to allocate small vectors on the stack instead of on the heap.

Currently the user can pass a WsClient and a SaltyClient instance to the task loop without going through the handshake. Maybe we can prevent that?