Are timers safe for asp.net apps?

[Brock Allen]

Yes it will. But what if no one requests that data in the meantime? You've
wasted effort for something that's not needed. That's why I suggested the
lazy load approach. You still have timing issues, too. Say the cache times
out, the item is removed and then your callback happens, but it hasn't yet
recreated the item in the cache... And then a page comes along and tries
to read the cache. You still have to wite the code in the page to check for
null and go back to the DB to reload it.

-Brock
DevelopMentor
http://staff.develop.com/ballen

 

[jensen bredal]

Yes it will. But what if no one requests that data in the meantime? You've
wasted effort for something that's not needed. That's why I suggested the
lazy load approach. You still have timing issues, too. Say the cache times
out, the item is removed and then your callback happens, but it hasn't yet
recreated the item in the cache... And then a page comes along and tries
to read the cache. You still have to wite the code in the page to check
for null and go back to the DB to reload it.

Well the second reason has convinced me that "Lazy load" has to be the way
to go.

Many Thanks

JB