| Name | Description |
|---|---|
| Controller | The `Controller` class is the fundamental building block of your application's request/response cycle. Controllers are organized around a single logical entity, usually one or more model classes (i.e. `lithium\data\Model`) and are tasked with performing operations against that entity. |
| DispatchException | This exception covers a range of scenarios that generally revolve around attempting to dispatch to something which cannot handle a request, i.e. a controller which can't be found, objects which aren't callable, or un-routable (private) controller methods. |
| Dispatcher | `Dispatcher` is the outermost layer of the framework, responsible for both receiving the initial HTTP request and sending back a response at the end of the request's life cycle. |
| Request | A `Request` object is passed into the `Dispatcher`, and is responsible for identifying and storing all the information about an HTTP request made to an application, including status, headers, and any GET, POST or PUT data, as well as any data returned from the `Router`, after the `Request` object has been matched against a `Route`. Includes a property accessor method (`__get()`) which allows any parameters returned from routing to be accessed as properties of the `Request` object. |
| Response | A `Response` object is typically instantiated automatically by the `Controller`. It is assigned any headers set in the course of the request, as well as any content rendered by the `Controller`. Once completed, the `Controller` returns the `Response` object to the `Dispatcher`. |
