Earlier quoted context omitted.
I think Gun has very similar philosophy, e.g. it is connection oriented and does not impose pooling and such.
Gun starts a process for each connection. The main idea for Mint was to not do this so that users can choose their own process structure.
Mint, a new HTTP library for Elixir
51–58 of 58 posts
Re: Mint, a new HTTP library for Elixir
#52Earlier quoted context omitted.
> it never ceases to amaze me why some HTTP libs don't have TLS as a given Separation of concerns. TLS termination is something that can be done separately, and at scale you want to separate it anyway.
For a server, sure, but for a client?
Re: Mint, a new HTTP library for Elixir
#53Earlier quoted context omitted.
No it doesn't. All you have to do is search and you get relevant results. Look through your library list, it's pretty common for the names to only make sense in context.
actually, if you need it fast, you can just duckduckgo "mint !hexpm"
Re: Mint, a new HTTP library for Elixir
#54Re: Mint, a new HTTP library for Elixir
#55Re: Mint, a new HTTP library for Elixir
#56What does Mint provide over, say, HTTPoison? Still can't quite grok what it's offers.
Requests made with HTTPoison are passed to the library’s own connection pool whereas requests made with Mint are handled in the same process. While HTTPoison is great for most use cases, Mint is a promising solution for anyone who has specific control flow requirements. I’m interested in this for some of the uglier API integrations I maintain where an ordered chain of requests must be made with no guarantee of delive…
Re: Mint, a new HTTP library for Elixir
#57People are the worst at naming products. Why call it Mint when there is already an insanely popular Mint.com financial software. It makes Googling/searching for product relevancy near impossible. It's like try to search for Firefox on Android vs Firefox on a desktop information.
Not to mention Linux Mint.
Re: Mint, a new HTTP library for Elixir
#58I'm liking the trend of designing runtime-behaviour agnostic libraries in Elixir. We get such powerful runtime capabilities with OTP, but indulged in the wrong context our cool OTP processes can be imposing assumptions onto our users. I'd like to see some kind of generic HTTP contract or REST-API client builder library next so we can have swappable HTTP adapters (e.g. Mint/Hackney). I don't want to depend on a librar…