How is web.config cached, to memory or disk?

[Gery D. Dorazio]

MS docs say that the web.config information is cached? Where?...to memory or
disk or both as part of LRU? Is this cache mechanism controllable...e.g. if
it is part of a least recently used algorithm and then it is written to disk
can this be overridden? Any article links would be appreciated.

Thanks,
Gery

--
Gery D. Dorazio
Development Engineer

EnQue Corporation
1334 Queens Road
Charlotte, NC 28207
(704) 377-3327

 

[Joe Fallon]

To my knowledge it is read into RAM on first access.
Then the cache is invalidated if the file is changed on disk and it is
re-read.

I heard that this is true for any file with a .config extension - never
tried it though.

 

[Hans Kesting]

To my knowledge it is read into RAM on first access.
Then the cache is invalidated if the file is changed on disk and it is
re-read.

If the web.config changes, the application is restarted.

I heard that this is true for any file with a .config extension -
never tried it though.

I doubt this: for web.config there is a specific class that acts as an interface.
For any other file you will have to write your own code. If your code
reloads that file every time, then it *is* reloaded from disk. I don't think
there can be a general mechanism to invalidate some unknown object
that you happen to initialize from some .config file.
Those file *are* treated special in an other way: access via the webserver
is prohibited, so visitors can never read any .config file that mey be on your site.

Hans Kesting

 

[Scott Allen]

Yes, in my experience the site.config map for navigation maps in 2.0
doesn't work this way currently.