github-personal/firezone
1
0
Fork 0
mirror of https://github.com/outbackdingo/firezone.git synced 2026-01-27 10:18:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

refactor: sans-io minor fixes (#5694)

Browse Source 
Just some minor nits I noticed after going live, before we post to
socials.
This commit is contained in:
Jamil
2024-07-03 13:57:04 -07:00
committed by GitHub
parent ecb38dedf9
commit 2db32c247f
1 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
website/src/app/blog/sans-io/readme.mdx
View File

@@ -2,13 +2,13 @@ import Image from "next/image";
import Alert from "@/components/DocsAlert";
At Firezone, we build secure remote access that scales, be it from your Android
phone, MacOS computer or Linux server. At the core of these apps sits a
connectivity library - aptly named
[`connlib`](https://www.github.com/firezone/firezone/tree/main/rust/connlib) -
that manages network connections and WireGuard tunnels to secure your traffic.
After several iterations, we’ve landed on a design that we are extremely happy
with. It gives us blazingly fast and exhaustive tests, deep customisation and
overall high assurance that it does what we want it to do.
phone, MacOS computer or Linux server. At the core of each app sits a
connectivity library — aptly named
[`connlib`](https://www.github.com/firezone/firezone/tree/main/rust/connlib)
— that manages network connections and WireGuard tunnels to secure your
traffic. After several iterations, we’ve landed on a design that we are
extremely happy with. It gives us blazingly fast and exhaustive tests, deep
customisation and overall high assurance that it does what we want it to do.
`connlib` is built in Rust and the design we are talking about is known as
sans-IO. Rust's premise of speed and memory-safety makes it a great choice for
@@ -148,10 +148,10 @@ non-blocking IO.
How do we apply the dependency inversion principle then? We introduce
abstractions! When we call `UdpSocket::send`, what data are we actually passing?
The payload, a `SocketAddr` and - implicitly - the socket itself. The socket can
also be identified by means of a `SocketAddr`: The one we bound to earlier in
our application. Let's package these three things up into an abstraction. Meet
`Transmit`:
The payload, a `SocketAddr` and — implicitly — the socket itself.
The socket can also be identified by means of a `SocketAddr`: The one we bound
to earlier in our application. Let's package these three things up into an
abstraction. Meet `Transmit`:
```rust
pub struct Transmit {