The Application Structure

To understand how Veronica works, we first need to have a general idea of how the framework is structured and who does what. To do so, we are now going to follow the life-cycle of an Http request as it gets processed by a Veronica based application, to see how a response is generated.

• The Application object constitutes the starting point of the development of a Veronica based web-app. It contains a basic implementation of an Http Server and the Application Router. The application manages the Http Server, and when a request is received it gets parsed and transformed into a Request object. The Request is then passed down to the Router.
• The Router receives the Request from the Application and is now responsible for establishing which Route will handle the Request and generate a Response. For more information about the routing process, check out the documentation.
• Once a Route receives a Request, it will proceed to generate a Response. The generation of a Response happens through a process which is divided into several stages, which together constitute the Route's Request Pipeline. In fact, every Route has a Pipeline assigned to it which is responsible for generating the Response. For more information about the Request Pipeline, check out the documentation.
• Once a Response is generated by the Route's Pipeline, the Application passes it to the Http Server which sends it back to the client.