I want to take a quick look at the role the Request object will play in the overall grand scheme of Constrictor. As its name defines, the Request represents the entire request, from start to finish. This means that it will both handle the request and serve as the way for controller methods to access headers and sent data back to the client. While this sort of lumping is what drove me away from Rails (Putting both querying and result data in the same Model class.), I feel that, in this case, designing everything under the same system will make the Request be a unifying hub for all of the information instead of a convoluted, inelegant solution that Rails’ Models turned out to be. However, I will be constantly evaluating how the Request class performs, and, if necessary, will be placing the actual handling of a request back under the roof of the main Constrictor class.