I am developing an ASP.Net application using C#, under Visual Studio 2008.
I want to be able to keep a cache of certain objects, but I only want the cache to last per page request, so that each new page request goes and rebuilds the cache again.
I have two Projects in my Visual Studio Solution, one is the Asp.Net application, and the other is my "Data Layer", as such, which takes the form of a class library. The class library gets built as a DLL and referenced by the Asp.Net application.
I want to contain the object cache within the Data Layer class library (as the Data Layer needs to manipulate it, and the Asp.Net application does not), but the problem is that this class library seems to stay in memory, presumably because it's a DLL. This means that the object cache stays in memory, on-between page requests, which I don't want.
I figure there are the possible solutions, but I can't figure out how to write them in code...
1. Stop the DLL from staying in memory in-between page requests. This isn't ideal, as I'd probably like some things in the class library (such as a connection to a SQL Server) to stay in memory all the time.
2. Fire off an event before or after all page requests to clear the object cache. Maybe this could be done as an event hook in a Master Page, but it would be nice if there was a more global method of hooking into the beginning or end of all page requests.
3. ?
Can anybody please help me? I am willing to explore most suggestions, but this is quite a big project already so I may be restricted a little in what I can try.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Had a look at HttpModules, and found them a little too complicated, and possibly innapropriate for the situation.
I've actually found my own solution. I didn't realise that I could use the attached code. I just didn't know about the existence of HttpContext.Current.Items property. D'oh!
For those who might be interested, "HttpContext.Current.Items
Business Accounts
Answer for Membership
by: McExpPosted on 2008-04-15 at 14:34:28ID: 21363062
A solution for option 2 would be to write a Http Module, this could then be configured to fire on all page requests.
http://www.15seconds.com/i