Mint Disrupting HTTP clients
summary
Mint is an HTTP/1 and HTTP/2 client for Elixir that exposes a process-less client as a plain connection struct wrapped around a TCP/SSL socket, making requests fully streaming responses and enabling multiple in-flight requests (HTTP/2 multiplexing, server push, ping/pong, cancelation, backpressure). It merges SSL options safely and ships a default certificate store so it’s safe by default. Version 1.2 is stable; pooling is left to Finch (nimble_pool) because multi-host proxy pooling isn’t implemented in Mint itself.
AI-written summary · about
chapters (17)
- 0:00Start
- 2:16Why Did We Write this Client
- 6:42Start an Http Connection with Mint
- 8:41Request Ref
- 9:57Responses
- 14:14Security
- 19:35Tunnel Proxy
- 20:06Support for Hp2
- 21:43Server Pushes
- 25:12Use Cases
- 27:09Stage Pooling
- 27:45Challenges
- 29:41Single Host Pools and Multi-Host Pools
- 31:39Features of Mint
- 32:06Future
- 32:41Resources
- 34:44How Does Mint Being Processors Handle Http Keeper Live Connections That Are Supposed To Be Kept Open
related talks
39mScaling HTTP Connections
28mHow to Inject Faults into Common HTTPS Clients and Services
01h 52m100% Fast and Resilient Microservice with RSocket
15mElixir: A High-performance and Low-cost Approach to Managing Hardware/Software Hybrid
11mMultiplex tcp requests through Envoy HTTP/2 stack
35mLight Clients Aren't Dead
06mNetwork-level Anonymity and Transaction Privacy
20mmmTLS: Scaling the Performance of Encrypted Network Traffic Inspection