river Alternatives - Elixir HTTP

Popularity

6.2

Declining

Activity

0.0

Declining

Stars 78

Watchers 6

Forks 3

Last Commit

Monthly Downloads: 18

Programming language: Elixir

License: MIT License

Tags: HTTP

Latest version: v0.0.7

river alternatives and similar packages

Based on the "HTTP" category

gun

9.6 8.2 river VS gun

HTTP/1.1, HTTP/2 and Websocket client for Erlang/OTP.
Crawler

9.5 3.1 river VS Crawler

A high performance web crawler in Elixir.
mint

9.4 7.4 river VS mint

Functional HTTP client for Elixir with support for HTTP/1 and HTTP/2.
scrape

8.7 8.2 river VS scrape

Scrape any website, article or RSS/Atom Feed with ease.
Ace

8.4 3.8 river VS Ace

HTTP web server and client, supports http1 and http2.
PlugAttack

8.0 1.1 river VS PlugAttack

A plug building toolkit for blocking and throttling abusive requests
neuron

7.7 5.3 river VS neuron

A GraphQL client for Elixir.
Crawly

7.5 8.0 river VS Crawly

high-level web crawling & scraping framework for Elixir.
webdriver

7.4 0.0 river VS webdriver

This is an implementation of the WebDriver protocol client. It currently supports PhantomJS, FireFox, ChromeDriver and remote webdriver servers (e.g. Selenium).
web_socket

6.8 0.0 river VS web_socket

An exploration into a stand-alone library for Plug applications to easily adopt WebSockets.
spell

6.6 0.0 river VS spell

Spell is a Web Application Messaging Protocol (WAMP) client implementation in Elixir.
cauldron

6.1 0.0 river VS cauldron

An HTTP/SPDY server as a library.
http_proxy

5.3 2.3 river VS http_proxy

Multi port HTTP Proxy.
explode

4.5 1.0 river VS explode

An easy utility for responding with standard HTTP/JSON error payloads in Plug- and Phoenix-based applications.
bolt

4.4 0.0 river VS bolt

Simple and fast http proxy.
ivar

3.5 0.0 river VS ivar

A lightweight wrapper around HTTPoison that provides a fluent and composable way to build http requests.
sparql_client

3.3 3.0 river VS sparql_client

A SPARQL protocol client for Elixir.
uri_template

3.1 0.0 river VS uri_template

RFC6570 compliant URI template processor for Elixir.
etag_plug

3.1 0.5 river VS etag_plug

A simple to use shallow ETag plug.
Tube

2.9 0.0 river VS Tube

Pure Elixir WebSocket client library.
fuzzyurl

2.8 0.0 river VS fuzzyurl

An Elixir library for parsing, constructing, and wildcard-matching URLs. Also available for Ruby and JavaScript.
httprot

2.8 0.0 river VS httprot

HTTP client library.
yuri

2.3 0.0 river VS yuri

Simple struct for representing URIs.
mnemonic_slugs

2.0 0.0 river VS mnemonic_slugs

A memorable, mnemonic slug generator in Elixir.
uri_query

2.0 0.0 river VS uri_query

URI encode nested GET parameters and array values in Elixir.
Ralitobu.Plug

1.4 0.0 river VS Ralitobu.Plug

Elixir Plug for Ralitobu, the Rate Limiter with Token Bucket algorithm
lhttpc

1.4 0.0 river VS lhttpc

A lightweight HTTP/1.1 client implemented in Erlang.
plug_wait1

0.8 0.0 river VS plug_wait1

Plug adapter for the wait1 protocol.
http_digex

0.6 0.0 river VS http_digex

A module to create basic digest HTTP auth header.

Do you think we are missing an alternative of river or a related project?

Add another 'HTTP' Package

Popular Comparisons

README

River

NOTE: River is a work in progress and should be considered extremely beta.

River is a general-purpose HTTP client with eventual hopes of full HTTP/2 support (along with support for HTTP/1.1). It is built from the ground up with three major goals:

be fully compliant with RFC 7540
be simple and straightforward to use, in the vein of HTTPoison
be awesome, in the same way that Go's http library (which has built-in, transparent support for HTTP/2) is awesome.

Installation

Add River to your list of dependencies in mix.exs:
```
def deps do
[{:river, "~> 0.0.6"}]
end
```

Ensure River is started before your application:

def application do
[applications: [:river]]
end

Caveats

Currently, River only knows how to make HTTP/2 requests to https:// endpoints. Soon, I'll add the ability to make a request via the Upgrade header so that requests to http:// endpoints will work as well.
River doesn't currently speak HTTP/1.x. Once I finish up basic HTTP/2 support, HTTP1.x is next on the roadmap. The goal when using River in your project is that you should not need to know whether the underlying connection is using HTTP/2 or HTTP/1.x.
River is as beta as it gets, and under active development with no promises of anything being backwards compatible 😬 (until we hit v1.0, of course)

Goals

[x] Basic HTTP/2 support
[ ] HTTP/1 --> HTTP/2 upgrading
[ ] Full HTTP/2 support
[ ] Full HTTP/1.x support

Basic Usage

Simple GET

River.get("https://http2.golang.org/")
=> {:ok,
 %River.Response{__status: :ok,
  body: "<html>\n<body>\n<h1>Go...",
  closed: true, code: 200, content_type: "text/html; charset=utf-8",
  headers: headers: [{":status", "200"},
                     {"content-type", "text/html; charset=utf-8"},
                     {"content-length", "1708"},
                     {"date", "Fri, 30 Sep 2016 04:26:34 GMT"}]}}

Simple PUT

River.put("https://example.com/", "hello world")
=> {:ok, %River.Response{...}}

Request with timeout

# timeout unit is milliseconds
River.get("https://http2.golang.org/", timeout: 10)
=> {:error, :timeout}

river

An HTTP/2 client that is lightweight and lightning fast.