Comment #45 on issue 6688 by bekkra: Allow the user to set the disk cache location independently of the profile http://code.google.com/p/chromium/issues/detail?id=6688
I agree fully to the idea of using a "visible" configuration for the cache. There are two reasons for taking the road over the command line: The first is the obvious speed of implementation of the command line change. It is a low-risk, easily tested change with full return. Needless to say, I want this for myself because this lets me use the browser where its cache storage policy would otherwise stop me. The second is that a change in the GUI needs careful consideration, which means quite a few discussions, and in the implementation phase, much more error-prone changes. The changes require testing and a review process which is more elaborate than in the case of the command line switch. Given the nature of the change, it is more to regard as extra functionality, and I see that our resources are better spent on actual bugs than on adding infrequently used features. While I see that we can provide a "good enough" feature by the command line change to little effort, I can only see a GUI change as a "sometime in the future" addition. I would love to find acceptance for this new option in the "under the hood" tab, and I would be very pleased to work with it. In the meantime, though, having the functionality in place and accessible through the command line, gives that "good enough for the moment" feeling. :) // -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
