On 7/16/2012 10:40 AM, Jacopo Cappellato wrote:
As a first step in the review/cleanup of the "images" component I am proposing to move its content, i.e. the "images" webapp, to the framework/resources, transforming it into a component that will mount the "images" application. This is a trivial change but in my opinion "resources" is a more appropriate component name than "images".
I agree.
The next steps for the future will be to move out of the framework the folders in the "images" application that are specific to applications (somewhere under runtime seems a good approach).
Some of the application-specific content could be used by other applications, so it should stay in the resources component. Anything that is truly application-specific should be kept in the application. The application-specific content can be added to the application's URL path. If that causes problems with other applications trying to access it (I'm thinking of the product content), then we might need to re-engineer some things to accommodate that. Putting content in the runtime folder sounds odd to me.
-Adrian
