G
Guest
In one of our ASP.NET Pages, we are starting a new background thread that we
do not need to go and get any status on or use after the page finishes. The
thread merely does some background stuff on its own and finishes on its own,
no feedback back to the user (by design). Within that thread however, some
items need to be accessed and/or inserted into the Cache for possible
subsequent processing by another page. Many examples I see of background
threads include access to the Session object however in our tests here we
found we could not access the Response or Request objects in a background
thread, which is by design.
We passed in the Cache object as a property to our background thread and can
access it just fine, but we wanted to know if this was an okay way to access
the Cache from a background thread or are there better ways of accessing
Cache from a background thread?
Thanks so much I appreciate it!
Christopher
do not need to go and get any status on or use after the page finishes. The
thread merely does some background stuff on its own and finishes on its own,
no feedback back to the user (by design). Within that thread however, some
items need to be accessed and/or inserted into the Cache for possible
subsequent processing by another page. Many examples I see of background
threads include access to the Session object however in our tests here we
found we could not access the Response or Request objects in a background
thread, which is by design.
We passed in the Cache object as a property to our background thread and can
access it just fine, but we wanted to know if this was an okay way to access
the Cache from a background thread or are there better ways of accessing
Cache from a background thread?
Thanks so much I appreciate it!
Christopher