Accessing Application State on a Cache Expiration

[Natty Gur]

Hi,

You can’t access the HttpContext.Current because when the callback
function call there isn’t any client request or to be more accurate the
callback isn’t attach to any request. To overcome it create private
member of application type in the global class and set it to the
application when the application start. Use the application private
member.

Check out my sample:
[url]http://www.developersdex.com/gurus/code/653.asp[/url]

Natty Gur, CTO
Dao2Com Ltd.
34th Elkalay st. Raanana
Israel , 43000
Phone Numbers:
Office: +972-(0)9-7740261
Fax: +972-(0)9-7740261
Mobile: +972-(0)58-888377


*** Sent via Developersdex [url]http://www.developersdex.com[/url] ***
Don't just participate in USENET...get rewarded for it!

[John McDowell]

>

> You can't access the HttpContext.Current because when the callback
> function call there isn't any client request or to be more accurate the
> callback isn't attach to any request. To overcome it create private
> member of application type in the global class and set it to the
> application when the application start. Use the application private
> member.
>

Hmmm. That's kinda what I figured I'd have to do (except I have to
use a Public Static (Shared in VB) as I need to get at it from several
classes). Thanks for the info.

You don't need to go through all that for your example though. Just
use System.Web.HttpRuntime.Cache to access the Cache from anywhere,
like a callback not attached to a request in a different class.

That's why I kinda figured there's be another way to get to the
ApplicationState, since they made the Cache available.

John