This post originated from an RSS feed registered with .NET Buzz
by Paschal.
Original Post: Caching, why it have to be so complicated ?
Feed Title: help.net
Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/pleloup/Rss.aspx
Feed Description: .Net for mankind !
Well I have a subject where I have a lot to learn, and it's caching. For the moment I don't really get it. I tried to use some cache functions in some of my projects, but I failed almost all the time.
I can't really find a clever article on all the different options, and it seems that the Cache class in .Net is overcomplicated. I discovered that for example timespan is more important than I could imagine, and it's really hard to tune up precisely the different parameters to have something really working and universal. I mean working well with the different browsers, different platforms, etc...
Last time I used the server cache, it was working well for a week, and suddenly I had to deal with a lot of Internal errors, you know the so infamous error you can't catch.
I removed the cache and now it's working very well. Of course the performances are surely not the same, but I can't afford any crash on a live website.
Unless somebody has a great web link on the subject, I give up on this for the moment.
Previous Topic
