At 360 in Atlanta I had the priveledge of meeting and talking with Joe Berkovitz, Chief Architect for Allurent, Inc.  As an increasing number of projects have made their way my way, I began to investigate new architectures for use when implementing them.  Of particular interest is Joe's MVCS architecture.

 
Similar to Cairngorm, MVCS is a MVC-based architecture.  However, where Cairngorm tends to make use of Singletons when creating the model, and controllers, MVCS seems to move away from Singletons.  Joe explains this decision in his Adobe Developer Connection article at http://www.adobe.com/devnet/flex/articles/blueprint.html.

 
I would recommend anyone interested in MVC-based architectures to check out the article.  I have been using Cairngorm for the majority of our projects during the past year and a half, and after reading the article, Im considering a shift towards MVCS.  Don't get me wrong, I think Cairngorm is solid and a useful architecture, but I like the ability to have localized controllers and models lower in the application stack.  My overall goal, afterall, is a highly reusable, scalable, and decoupled application framework. After some further reading, I noticed that the assets directory in the MVCS architecture is located within the Views directory.  I think that this is a logical place for view related assets to go.