Packages

raxx

0.0.1
1.1.0 1.0.1 1.0.0 1.0.0-rc.3 1.0.0-rc.2 retired 1.0.0-rc.1 retired 1.0.0-rc.0 retired 0.18.1 0.18.0 0.17.6 0.17.5 0.17.4 0.17.3 0.17.2 0.17.1 0.17.0 0.16.1 0.16.0 retired 0.15.11 0.15.10 0.15.9 0.15.8 0.15.7 0.15.6 0.15.5 0.15.4 0.15.3 0.15.2 0.15.1 0.15.0 0.14.14 0.14.13 0.14.12 0.14.11 0.14.10 0.14.9 0.14.8 0.14.7 0.14.6 0.14.5 0.14.4 0.14.3 0.14.2 0.14.1 0.14.0 0.13.0 0.12.3 0.12.2 0.12.1 0.12.0 0.11.1 0.11.0 0.10.5 0.10.4 0.10.3 0.10.2 0.10.1 0.10.0 0.9.0 0.8.2 0.8.1 0.8.0 0.7.1 0.7.0 0.6.0 0.5.2 0.5.1 0.5.0 0.4.3 0.4.2 0.4.1 0.4.0 0.3.0 0.2.0 0.1.0 0.0.1

Interface for HTTP webservers, frameworks and clients.

HexDocs

Current section

Files

Jump to
Readme
76 Versions
2 Dependencies
Dependants
Files
Activity
raxx README.md
Raw

README.md 

# Raxx



**A Elixir webserver interface, for stateless HTTP.**



Raxx exists to simplify handling the HTTP request-response cycle.

It deliberately does not handle other communication styles that are part of the modern web.



Raxx is inspired by the [Ruby's Rack interface](http://rack.github.io/) and [Clojure's Ring interface](https://github.com/ring-clojure).



Raxx adapters can be mounted alongside other handlers so that websockets et al can be handled by an more appropriate tool, e.g perhaps plug.



## Installation



If [available in Hex](https://hex.pm/docs/publish), the package can be installed as:



  1. Add raxx to your list of dependencies in `mix.exs`:



        def deps do

          [{:raxx, "~> 0.0.1"}]

        end



  2. Raxx apps/routers needs to be mounted Elixir/erlang server using one of the provided adapters. Instructions for this are found in each adapters README



    - [cowboy]() TODO for current setup see adapter tests.





### Principles



- Stateless HTTP request fulfill a valuable role in modern applications and will continue to do so.

- Handling other communication patterns as plug intends to do just adds complexity which is unnecessary on a whole class of applications.

- Use Ruby rack and Clojure ring as inspiration for naming but be happy to break away from historic CGI-style header names.

- Surface utilities so that it can be used in general HTTP based applications