aquatic_ws: upgrade to tungstenite 0.11

Cargo.lock

@@ -300,9 +300,9 @@ dependencies = [
 
 [[package]]
 name = "base64"
-version = "0.11.0"
+version = "0.12.3"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "b41b7ea54a0c9d92199de89e20e58d49f02f8e699814ef3fdf266f6f748d15c7"
+checksum = "3441f0f7b02788e948e47f457ca01f1d7e6d92c693bc132c22b087d3141c03ff"
 
 [[package]]
 name = "bendy"
@@ -1738,9 +1738,9 @@ dependencies = [
 
 [[package]]
 name = "tungstenite"
-version = "0.10.1"
+version = "0.11.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "cfea31758bf674f990918962e8e5f07071a3161bd7c4138ed23e416e1ac4264e"
+checksum = "a5c7d464221cb0b538a1cd12f6d9127ed1e6bb7f3ffca98fb3cd4c6e3af8175c"
 dependencies = [
  "base64",
  "byteorder",

TODO.md

@@ -30,6 +30,7 @@
 * test transfer again with changes made:
   * crossbeam-channel
   * ipv6/ipv4 mapping
+  * tungstenite 0.11
 * is 'key' sent in announce request? if so, maybe handle it like in
   aquatic_http (including ip uniqueness part of peer map key)
 * established connections do not get valid_until updated, I think?

aquatic_ws/Cargo.toml

@@ -32,7 +32,7 @@ serde = { version = "1", features = ["derive"] }
 serde_json = "1"
 socket2 = { version = "0.3", features = ["reuseport"] }
 simplelog = "0.8"
-tungstenite = "0.10"
+tungstenite = "0.11"
 
 [dev-dependencies]
 quickcheck = "0.9"