Rack (web server interface)
 |
|
| Original author(s) | Christian Neukirchen |
|---|---|
| Developer(s) | James Tucker, Josh Peek, José Valim, Michael Fellinger, Aaron Patterson, Santiago Pastorino, Konstantin Haase |
| Stable release |
1.5.1 / January 28, 2013
|
| Operating system | Cross-platform |
| Type | Middleware |
| License | MIT License |
| Website | rack |
Rack provides a modular and adaptable interface for developing web applications in Ruby. By wrapping HTTP requests and responses it unifies the API for web servers, web frameworks, and software in between (called middleware) into a single method call.
Rack is used by many Ruby web frameworks and libraries, such as Ruby On Rails and Sinatra. It is available as a Ruby Gem.
Rack has already inspired a JavaScript framework (jackjs) and a Perl one (Plack), a Common Lisp one (Clack), and has resulted in the Ruby developer quasi-standard of "rack-compliant".
It was also cited as an inspiration for OWIN.
The characteristics of a Rack application is that the application object responds to the call method. The call method takes in the Environment object as argument and returns the Rack response object.
The environment that is taken as argument by the call method refers to an object that has:
a) Information on the HTTP Request This includes the information like:
b) Rack specific information This includes the information like
In case the application is being used as a middleware, the environment can have objects that would provide session information, logging capabilities, information on the size of the data that can be used for read and writes etc. In addition to these, the server can store their own data in the environment.
The rack server object returns a response which contains three parts: the status, headers and the body.
Rack::Response provides a convenient interface to create a Rack response. The class Rack::Response is defined in lib/rack/response.rb. To use the Response class, instantiate it from the middleware layer down the stack. It can be used to modify the cookies.
Rack makes it easy to add a chain of middleware components between the application and the web server. Multiple middleware components can be used in the rack which modifies the request/response before handing it over to the next component. This is called middleware stack.
The Rack server adds multiple middle middleware by default for the functionalities like showing exception with all the details, validating the request and responses according to the Rack spec etc.
...
Wikipedia