lhttpc
mint
Our great sponsors
| lhttpc | mint | |
|---|---|---|
| - | 3 | |
| 1 | 1,328 | |
| - | 1.2% | |
| 0.0 | 6.9 | |
| about 8 years ago | 9 days ago | |
| Erlang | Elixir | |
| BSD 3-clause "New" or "Revised" License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lhttpc
We haven't tracked posts mentioning lhttpc yet.
Tracking mentions began in Dec 2020.
mint
-
Unpacking Elixir: Resilience
One example is HTTP libraries.
For instance, take Mint (https://github.com/elixir-mint/mint):
> Mint is different from most Erlang and Elixir HTTP clients because it provides a process-less architecture.
Mint is a low-level library which doesn't make attempt to manage processes (including HTTP pooling).
In contrast, Finch (which builds on top of Mint) includes pool management:
https://github.com/elixir-mint/mint#connection-management-an...
It can take someone a bit off guard when they realise that the library they use provide a "default pool" they were not aware of, and that it can become a bottleneck etc.
-
How to implement a disk cache plugin for Elixir's Req HTTP client?
> no error checking at all
Functions that raise always end in `!` in Elixir, or at least they should. Most have alternatives that return error tuples instead which you can pattern match on (this is what I recommend). You can read the docs for `get/2` (as opposed to `get!/2` which raises) here: https://hexdocs.pm/req/Req.html#get/2.
A common pattern is for the `!` version to call the version that doesn't raise, check the result, and raise on error, which is the case here: https://github.com/wojtekmach/req/blob/9de30de0df481ee557ccc...
> and if "body" is JSON, how do you even get the raw body, or can you?
You would set `decode: false` when calling `get!/2: https://hexdocs.pm/req/Req.html#new/1. You can also set this as configuration with https://hexdocs.pm/req/Req.html#default_options/1.
As a closing note I'll mention that Req is intended to be a very high-level, scripting-friendly requests library, similar to Requests in Python. If you don't want conveniences like Req provides, you can either turn them off or use something different, like Finch (which Req is based on, https://github.com/sneako/finch). Other than Req and Finch I'm personally only familiar with HTTPoison, which is significantly older than all of the libraries derived from Mint (like Finch and Req, https://github.com/elixir-mint/mint) but still works. There are many others though, like Gun and Tesla and such.
- ElixirのHTTPクライアントでお天気情報を取得したい(2022年)
What are some alternatives?
gun - HTTP/1.1, HTTP/2, Websocket client (and more) for Erlang/OTP.
finch - Elixir HTTP client, focused on performance
hackney - simple HTTP client in Erlang
elli - Simple, robust and performant Erlang web server
Crawly - Crawly, a high-level web crawling & scraping framework for Elixir.
httpoison - Yet Another HTTP client for Elixir powered by hackney
http_proxy - http proxy with Elixir. wait request with multi port and forward to each URIs
spell - Spell is a Web Application Messaging Protocol (WAMP) client implementation in Elixir. WAMP is an open standard WebSocket subprotocol that provides two application messaging patterns in one unified protocol: Remote Procedure Calls + Publish & Subscribe: http://wamp.ws/
ivar - Ivar is an adapter based HTTP client that provides the ability to build composable HTTP requests.
cauldron - I wonder what kind of Elixir is boiling in there.
uri_template - RFC 6570 compliant URI template processor for Elixir