Search Results for "option"

...There are a number of supported options(not to be confused with the HTTP options method), documented here, that can be added to your request. The example below shows the use of the :ssl and :recv_timeout options for a post request to an api that requires a bearer token. The :ssl option allows you to set options accepted by the Erlang SSL module, and :recv_timeout sets a timeout on receiving a response, the default is 5000ms.

Elixir WebRTC is an Elixir implementation of the W3C WebRTC API for building real-time communication features in Elixir applications. It gives developers a way to create peer connections, exchange media, and work with browser-compatible WebRTC behavior from the BEAM ecosystem. The project is especially useful for applications that need live audio, video, or data communication without leaving Elixir. It can support DataChannels through an optional SCTP dependency, which extends its usefulness...

Keila is a fully open-source newsletter platform designed as a self-hosted alternative to services like Mailchimp or Sendinblue. It enables users to create and manage email campaigns, build customizable signup forms, and handle subscriber lists. Keila supports using a personal SMTP inbox for small-scale newsletters or integrating with major transactional email providers—AWS SES, Sendgrid, Mailgun, Postmark—for larger deployments. It offers a sleek WYSIWYG editor for campaign creation,...

Erlang and Elixir make it very easy to send messages between processes even across the network, but there are a few pitfalls. Sending a message to many PIDs across the network also copies the message across the network many times. Send calls cost about 70 µs/op so doing them in a loop eventually gets too expensive. Manifold distributes the work of sending messages to the remote nodes of the PIDs, which guarantees that the sending processes at most only calls send/2 equal to the number of...

...Jason follows the JSON spec more strictly, for example, it does not allow unescaped newline characters in JSON strings - e.g. "\"\n\"" will produce a decoding error. No support for decoding into data structures (the as: option). No built-in encoders for MapSet, Range and Stream. No support for encoding arbitrary structs - explicit implementation of the Jason.Encoder protocol is always required. Different pretty-printing customization options (default pretty: true works the same).