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. 🚀
https://t.co/GMTZc3e42l
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)
https://t.co/mM05SouJ4p
#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!
https://t.co/2EKpK1kxNy
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
https://t.co/xExP7ot84m
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: https://t.co/GNZEhk1eh0
With hyper's 1.0 rc1 recently out (the #rustlang HTTP library), we're moving into the hyper Polish Period 💅: https://t.co/03bPxlLrd9
Come join us!
🦀 #rust#opensource
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!
https://t.co/1XB8dOTPdN
I streamed a discussion of converting hyper's 1.0 roadmap into issues, giving background for different parts. Here's a more permanent recording: https://t.co/3dxcKfLrdR
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 https://t.co/uDcaoPVMNF.
Been getting set up and testing today.