| Category: Linux / Miscellaneous |
| Watchers: 4 |
| Star: 105 |
| Fork: 2 |
| Last update: Aug 4, 2022 |
Twitter if you like this project
It uses TCP to try to connect to Chrome and Firefox (fallback) captive portal detection servers.
use std::time::Duration;
use online::*;
assert_eq!(online(None), Ok(true));
// with timeout
let timeout = Duration::new(6, 0);
assert_eq!(online(Some(timeout)), Ok(true));
It seems to me that having this crate be async may be a bit heavyweight, especially if someone is just trying to check if a user is online (no cross-thread communication is really necessary for most use cases i'd imagine).
reqwest handles this by having a blocking module that mirrors the top-level async API but without requiring an async runtime.
Would love thoughts on this!
Signature of online doesn't indicate in what timescale timeout is. One has to read documentation.
Duration better communicates fact that the argument is a timeout, and in what timescale is operates in. Stdlib had sleep_ms & park_timeout function. They were deprecated in favour of sleep & park_timeout that take Duration as argument. Mirroring this would make for less confusion.
Perform only the DNS resolution step.
Some ideas: https://www.golinuxcloud.com/commands-check-if-connected-to-internet-shell/
https://github.com/sindresorhus/is-online#ipversion
https://github.com/rust-unofficial/awesome-rust#logging https://github.com/awesome-rust-com/awesome-rust
