[rfc][icedtea-web][itweb-settings] Improve Icedtea-Web cache disk space

[Jacob Wisor]

On 09/09/2014 03:08 PM, Jie Kang wrote:
> ----- Original Message -----
>> On 09/08/2014 08:38 PM, Lukasz Dracz wrote:
>>>> As well, the ability to choose where icedtea-web downloads file should
>>>> still
>>>> be enabled even if cache has a limit of 0.
>>>
>>> Yes since it still downloads the files even if they are deleted after use.
>>> This provides the user with more choice on where they want the files to be
>>> temporarily.
>>
>> No, the UI components to choose a cache location should be kept disabled in
>> this
>> case indeed. 0 means *no* *cache*. Hence, IcedTea-Web should behave as
>> expected
>> which would be to store all downloaded resources in memory and if, and only
>> if,
>
> I disagree with disabling the cache location until this feature is implemented, or the feature for storing in a temporary directory is implemented

Then it's just about time to implement it, right? ;-) Not because of the UI 
rework but because IcedTea-Web has never behaved properly when the cache size 
was set to 0.

And yes, I admit that this feature/behavior should probably be implemented in 
another patch. Nevertheless, I would advise to go with disabling now and then to 
start working on this "memory only" behavior right away. Why? Because it is 
always best do to things "the proper way" as soon as possible. Usually, 
postponing things leads to even more problems later on. This is mainly because 
human beings are forgettable, tend to be lazy, and constantly lack time to do 
work. Yes, this includes me. ;-) So, this does not only apply to programming but 
to life in general.

@Lukasz
Please, do it "the proper way" now and honor us with a followup patch. When you 
will be done you will feel even better. :-)
Anyway, thank you for your resiliency on getting though with this patch already.

>> it should turn out to be impossible to implement proper working of
>> IcedTea-Web
>> without storing resources into files then they should be stored in the system
>> configured user's temporary directory. In other words, if cache size is 0
>> then
>> downloaded resources /could/ go into the user's temporary directory, although
>> this should practically never happen because IcedTea-Web should error out
>> with
>> an OutOfMemoryException before anything else in this case.
>> Also, the UI components denoting the cache location /could/ display the path
>> to
>> the user's temporary directory if cache size is 0.
>> So in any event the UI components must be disabled at cache size 0.