On Jul 16, 2012, at 11:50 AM, Adrian Crum wrote: >> 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.
The goal that I would like to achieve in the long term is the following: the framework/applications folders, once deployed should be read only and should not contain files that are generated at runtime; at the moment the images folder is an exception because, for example, when you upload an image the image is stored under framework/images/webapp/images (by default); for this I think that runtime would be a better fit. On the other hand I agree that static resources could be hosted in the respective component. But I am not planning to work on this sometime soon... we have time to think. Jacopo
