An RPC framework for Rust with a focus on ease of use.
-
Updated
Nov 13, 2020 - Rust
#
tokio
Here are 203 public repositories matching this topic...
A TCP/TLS load balancer for Linkerd 1.x.
-
Updated
May 31, 2018 - Rust
thedodd
commented
Aug 17, 2020
Here is a rough idea of what this test should do:
- It should be quite similar to the other tests which are currently in place.
- It should isolate a follower node, write a data to the cluster which will cause that node to fall behind into lagging state, but not into snapshotting state.
- It should then spawn a task which will continue to write data to the cluster.
- Just after it is spawne
Tokio binding for Tungstenite, the Lightweight stream-based WebSocket implementation
-
Updated
Nov 26, 2020 - Rust
Full-featured async (tokio-based) postgres connection pool (like r2d2)
-
Updated
Nov 17, 2020 - Rust
Async binding for Tungstenite, the Lightweight stream-based WebSocket implementation
-
Updated
Nov 9, 2020 - Rust
Layer 4 load balancer with dynamic configuration loading
-
Updated
Jul 15, 2020 - Rust
Full featured HTTP and Websockets library for rust/tokio
-
Updated
Dec 28, 2018 - Rust
A pure-Rust LDAP library using the Tokio stack
-
Updated
Nov 25, 2020 - Rust
psztoch
opened
Jan 31, 2020
Asynchronous ClickHouse client library for Rust programming language.
-
Updated
Nov 1, 2020 - Rust
Asynchronous Web framework for Rust
-
Updated
Nov 26, 2019 - Rust
A Redis Client for Rust based on Futures and Tokio
-
Updated
Nov 30, 2020 - Rust
Background job library for Rust supporting RabbitMQ
-
Updated
Nov 16, 2020 - Rust
[Mirror] RTMP streaming server written in Rust
-
Updated
Sep 30, 2020 - Rust
12
wafflespeanut
commented
Mar 5, 2019
It looks like Nitox doesn't support client verification as of now. I made some quick changes to pass TLS config to the native-tls connector. When I tested this, I'm getting:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: TlsError(Ssl(Error { code: ErrorCode(1), cause: Some(Ssl(Erro
Improve this page
Add a description, image, and links to the tokio topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the tokio topic, visit your repo's landing page and select "manage topics."
In terms of Telegram bot API the maximum polling time of
getUpdatesis referred to astimeout. That is if there are pending updates, Telegram will return them immediately. In the other case, it will wait for timeout seconds and then answer with an empty list.The telegram-bot Rust library has its own notion of timeouts. getUpdates' timeout [i