Sanstun removes internal buffering for simpler, more testable APIs
1 Oct 30 5:30 PM · 13d ago · 1 article · 2 posts · 3 sources · development 1 of 1
A key design decision in Sanstun was eliminating internal buffering—boringtun automatically established sessions and buffered packets, but Sanstun puts that responsibility on the caller. This simplifies both the interface and implementation, and aligns with sans-IO principles by removing side effects from the library.
“Just don't buffer in the library. It simplifies the interface and the implementation on both sides.”
FirezoneFirezone Developer of Sanstun
The whole story articlesposts the bright band is this development · numbered dots are the others · click one to jump
Reported in the same hours no headline names this development itself — these 1 claim were published in its stretch
-
first by HN Frontpage, 13d ago
What people said 10 voices · verbatim
-
> Async is not I/O. It can be used for I/O, but it's just a way of writing pure, deterministic state machines that keeps a logical flow together instead of scattered over a bunch of transitions.I argue that it is exactly opposite. Blocking threads are a much more natural way of thinking about concurrency.Quote from the erlang creator Joe…
-
> flow that crosses several state transitions (and may have other disjoint parts of the state updated in the meantime, via other transitions) now has to be rewritten as a (series of) state transitions, and can't be called from a blocking functionThis is incorrect. You can easily call that flow from a blocking function, just call it in a loop.What…
-
In principle, you are right. Async is not I/O. And yes, `async` functions compile to a deterministic state machine.The problem is, the moment you use `async`, your state machine reduces down to one API: `poll`. What if I want to change some state in-between two state transitions (i.e. between two `await` points)? Now I have to wire-in a channel to…
-
It was all going great until I read> The design also avoids problems like function coloring and plays well with Rust's ownership rules.Async is not I/O. It can be used for I/O, but it's just a way of writing pure, deterministic state machines that keeps a logical flow together instead of scattered over a bunch of transitions.Even if you choose to…
-
Without actual code solving an actual problem discussing this is all a bit wishy washy, but I think you're mixing 'levels'.The sans-io design here is about building reusable parts that any runtime or thread can drive and incorporate into the colored interface they expose.Function coloring is about (the annoyance when) composing interfaces designed…
-
From their website about their product:> Hardware does the heavy lifting.> Your operating system and network card take over the repetitive jobs whenever they can. Your CPU gets room to breathe, and your battery stays full longer.Where does this operating system run? Where does the power come from to run it if not battery?Pure rubbish ai slop.While…
-
One of the fundamentally great things about the Wireguard protocol is the simplicity. A small codebase can implement it, and that’s lead to some great libraries and innovation.Another great (and subtle) thing is the monotonically increasing sequence number. Note that it isn’t incrementing, like DTLS. This small thing makes it so much easier to…
-
I've recently been developing a VPN Manager implementation using Rust, and the underlying architecture also uses WireGuard. Currently, I'm using WireGuard gotatun developed by Mullvad.I wonder if you've tested any related data, such as performance curves, connection jitter, and so on, as well as things like security implementations.
-
Sweet, this is basically how I design my protocol implementations in rust as well.Way more testable, the bulk can be shared between async and blocking IO, it's a lot easier to completely ban unsafe in your dependencies (excepting std and core), etc.
-
Mullvad spun their own implementation off of boringtun as well (called gotatun[0])[0]
All 1 developments of Firezone releases Sanstun, a sans-IO WireGuard… →
Hacker NewsNewswiresMastodon