Determine the maximum size of the Chrome Internet users' temporary file cache.

How to programmatically determine the maximum size of the temporary files cache for Chrome Internet users?

We have a simple desktop application that the user runs to get a variety of information about the local computer to determine compatibility with our other software products. One of the requirements is that the user has at least 100 MB of free space allocated for temporary Internet files.

For example, if an IE 9 user has 200MB of files residing in his or her temporary Internet files and their setting is Disk Space to Use (the setting that exists in Internet Options → General - Browser History Settings ) set to 250MB, the reported number will be 50MB, (max cache size is the current cache size).

The desktop application reads the maximum size from "HKEY_CURRENT_USER \ Software \ Microsoft \ Windows \ CurrentVersion \ Internet Settings \ 5.0 \ Cache \ Content" and estimates the size of the temporary internet files simply by examining the size of the temporary internet files directory.

In Firefox 8, these parameters can be read from prefs.js in the Firefox user profile directory.

In Chrome, however, there is no obvious way to get this data programmatically. Yes, a user can view and report this information with "chrome: // net-internals /", but we aim to obtain this information without requiring any user input. Estimating the current size of a Chrome user's temporary internet caches cache is as easy as determining the size of their cache folder, but the maximum size setting was a hard nut to crack.

As far as I understand, Chrome's max cache size changes dynamically. If this value has an upper limit, that might be enough for my needs. For example, knowing that the maximum cache can be as high as 1 GB, I can calculate the size of the cache folder, subtract that from the 1 GB upper limit, and verify that the resulting amount of space exists on the hard drive.

However, I have yet to find any documentation to support any kind of upper limit, and I would still be much happier to have this information as reported by Chrome, rather than relying on a calculation that doesn't far exceed the estimate.

Thank!