Application Variables

whats discountASP.net's views on storing a variable in an application Variable, such as for a kind of cache for a web page, so it doesnt hit the database every time. Testing over the past week or so, I have not found any issues with it as far as server issues. But ... let me know, thanks.

its a small site also by the way, not many variables, not "that" much traffic. I can explain further if you want.
I like how fast the pages load though, instant!! It is not updated much.

I would think less server stress though, as if for say it is "cached" for 24 hours, then if the page gets 1000 hits, the database is only hit once every 24 hours ... instead of 1000 times? But then it still depends on memory, but,My test PC only has 128MB shared memory (shared with video), and no performance issues, so I imagine it would not be a problem?

This is Classic ASP and Access Database, but I will eventually upgrade, though it is not designed for that yet, It is an app I will be selling/giving awayto other developers that still use classic ASP. I will eventually convert it to ASP.net and SQL server also. Right now I am looking on whether I can convert it to a VBScript class, since it somewhat "caches"...and cacheing a com object is not advised, is this the same situation?? Though I may not evenhave to"cache" the object,I wont know until I get more into theconvertsion this weekeend.All subs and functions straight from classic ASP right now is about 2000+ lines, but that will lower considerably since I can reuse alot of code and clean it up, ALOT as a class file.

if you want to see how fast it loads as is, let me know...

thanks

Rory

Post Edited (roryknowles) : 11/13/2004 6:02:52 AM GMT