Continuing their series of "sneak peeks" at the coming functionality and features of the next generation of components from the Aura framework, their blog looks at the version 2 of Aura.Web. This component has been refactored because of the creation of the Aura.Dispatcher as well.

Aura.Web v1 took the parts of Solar related to web controllers and combined them into a single independent package. [...] In the Aura.Web case, it turns out extracting Aura.Dispatcher was the key to reducing the Aura.Web package contents. With Aura.Dispatcher, any object can be a controller, since it can dispatch to any method on any object (as well as dispatching to closures). In turn, there is no more need for the Aura.Web package to provide a base controller with interfaces for various implementations.

The rest of the post explains the two halves of the new Aura.Web version - the Request and Response - and what kinds of things are included in each. It also links each to the parts of the READMEs that deal with them, providing a bit more information.

On PHPMaster.com today Hari K T has spotlighted one of the components from the Aura framework, the Aura.Web component.

MVC is an acronym that means Model-View-Controller. In this tutorial I would like to introduce you to Aura.Web, the controller component of the Aura Library. Here I’ll show you how to use it to build your own controller, and also how to use a response transfer object to issue HTTP response headers, and integrate a templating engine like Mustache for rendering views.

He starts off with an overview of how the component is architected and how it is used to create controllers and what dependencies it needs injected. He talks about some of the objects and the methods they provide and includes some sample code for a basic "Index" controller. He shows how to integrate the Mustache templating engine for output and how to work directly with HTTP responses.