asp.net - Should I put custom AppSettings web.config data into the ApplicationState? -
i've got custom values in appsettings, in web.config file.
these values checked upon every request. (please ignore fact might bad/good thing .. that's out of scope of question).
eg.
so if every request checks web.config file value of key, be smart put application cache (eg. via global.asax) instead of checking value every request?
i'm assuming when read value appsettings, website physical read of web.config file? or information read memory when website starts , references appsettings information inmemory read .. not disk i/o read?
the webconfig cached. @ first request of website physical read. others requests use cache data. why when change web.config file , call request site have little delay, because information in web.config being recached.
Comments
Post a Comment