D
Dan Bass
The way I thought of caching is the generally known way, such as page
caching, sticking items in session or application variables or into the
viewstate. None of these really appealed to me for the purpose of this.
Apologies if this has caused a wasted journey to the solution.
No need to apologise... we're all learning. I don't know a quarter of what I
should..
So, one more question, with what I have here in this code, if I make the
"Folders" static, and I make a change to the database, I need to somehow
update the static folders. How can I trigger the update?
Ah, this is the question... Really. They should be initalised once (when IIS
starts?) and then left as readonly.
http://samples.gotdotnet.com/quickstart/aspplus/doc/stateoverview.aspx
If you're bothered about the refreshing bit, then perhaps have it done in a
session state rather than application. Then you can access it through your
page where ever you need to. Each time the user goes to the web site and in
turn creates a new session, the object will be refreshed.