Search Results for "xymon-client-4"

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...

Pusher server implementation is compatible with Pusher client libraries. Open Pusher implementation compatible with Pusher libraries. It's designed to be used as a single registered app with id, secret, and key defined on start. Poxa is a standalone elixir server implementation of the Pusher protocol. Docker images are automatically built by Docker Hub. They are available at Docker Hub. One can generate it using: docker build -t local/poxa. Poxa uses gproc extensively to register websocket...

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...