I have a branch that migrated the project to std.Io - Migrate to std.Io by lalinsky · Pull Request #66 · lalinsky/dusty · GitHub
It no longer depends on zio.
I’m not sure what is the best way forward, as we lost timeouts this way, but I think some hybrid solution with comptime hooks will be used.
I’ve released v0.3 of dusty, many changes, including the std.Io migration, included:
Timeouts on std.Io are back, but there is a special hook for zio, since timeouts are more efficient when using zio directly.
I’ve been testing the performance of the server, it was on par with hyper/rust, so I’m pretty happy with it.
That said, performance is not my priority. I really want this to be the most reliable/resilient HTTP server/client in the Zig ecosystem. I’m already running it in production on a couple of internal projects.
One small follow-up release, that adds native support for timeouts to the HTTP client, as more and more people keep looking for this. Plus native support for X-Forwarded-For reverse proxy hops for my own use.