Search Results for "tiny-http"

This library can be configured to handle encoding and decoding requests and responses automatically based on the accept and/or content-type headers. An Elixir OAuth 2.0 Client Library. This library can be configured to handle encoding and decoding requests and responses automatically based on the accept and/or content-type headers. The http client library used is tesla, the default adapter is Httpc, since it comes out of the box with every Erlang instance but you can easily change...

The flexible HTTP client library for Elixir, with support for middleware and multiple adapters. Tesla is an HTTP client loosely based on Faraday. It embraces the concept of middleware when processing the request/response cycle. Define module with use Tesla and choose from a variety of middleware. Tesla is built around the concept of composable middlewares. This is very similar to how Plug Router works. All HTTP functions, such as Tesla.get/3 and Tesla.post/4, can take a dynamic client...

HTTP client for Elixir, based on HTTPotion. HTTPoison uses hackney to execute HTTP requests instead of ibrowse. Using hackney we work only with binaries instead of string lists. First, add HTTPoison to your mix.exs dependencies. Add :httpoison to your applications list if your Elixir version is 1.3 or lower. You can also easily pattern match on the HTTPoison.Response struct. There are a number of supported options(not to be confused with the HTTP options method), documented here, that can...

... included directly from GitHub. The required assets are not included in the repo in build form and can therefore not be used. It is possible to build locally and use the generated package. (See Build manually for more information.) To view the web interface just enter http://<host>[:<port>]/ in the browser and it should show the :wobserver interface. The default port is 4001, but the port can be changed in the configuration.

An Elixir implementation of Facebook's GraphQL. This is the core GraphQL query parsing and execution engine whose goal is to be transport, server and datastore agnostic. In order to setup an HTTP server (ie Phoenix) to handle GraphQL queries you will need plug_graphql. Examples for Phoenix can be found at hello_graphql_phoenix, so look here for a starting point for writing your own schemas. Other ways of handling queries will be added in due course. Tokenization is done with leex and parsing...