hyper in curl needs a champion.
A backing vendor or distro that wants it.❤️
Why? Memory un-safety. Is. BAD.
A #rustlang HTTP backend in #curl has potential to make the internet safer. 🦀
But it needs a champion to back it, or it will go away. 🚀
seanmonstar.com/blog/hyper-i…
hyper v1.2.0 is released! 🚀
This includes some helpful new builder options:
- HTTP/1 max headers
- HTTP/2 initial send stream limits. (Check the note, this will adopt a conservative default in v1.3)
github.com/hyperium/hyper/re…#rustlang 🦀
And a release of #rustlang hyper-util v0.1.3 🚀
- Individually enable http1/http2 for the server-auto conns.
- Improve timer support in the legacy client.
- Fixes and more!
github.com/hyperium/hyper-ut…
New v0.14.25 release of #rustlang hyper! 🦀
- Backporting of some 1.0 APIs
- An opt-in `deprecated` way to prepare for 1.0
- Client mechanism to poison connections from the pool
github.com/hyperium/hyper/re…
I made a tracking issue for #rust#rustlang hyper's 1.0, to centralize a list of announcements, polish areas, current owners, and what is needed next: github.com/hyperium/hyper/is…
hyper v0.14.19 release is out now!
- HTTP/2 max header list option
- Improved content-length for HEAD responses
- C API improvements around header options
- Docs and refactors to tidy up🧹
❤️to the 8 new contributors that made this possible!
github.com/hyperium/hyper/re…
I streamed a discussion of converting hyper's 1.0 roadmap into issues, giving background for different parts. Here's a more permanent recording: piped.video/czIVMiuxlLw
As we start dev work on #rustlang's hyper 1.0, we need science to weed through the opinions. Is master always shippable, or always the bleeding edge?
When starting a new major version, does code go...
Considering streaming some #rustlang work on hyper, especially 1.0 planning, later this week on twitch.tv/seanmonstar.
Been getting set up and testing today.