Fromhttp://www.codeproject.com/Articles/146455/When-can-we-use-HttpContext-Current-Items-to-store
To answer this question in a single statement, you can useHttpContext.Current.Items
for very short term storage. By Short term storage we mean that this data is valid for asingle HTTP Request. There is a lot of confusion around regarding storing data inHttpContext.Current.Items
andstoring data in Session variable. In this blog post, I am going to describe what are the different scenarios where we can useHttpContext.Current.Items
and what is the exact difference with session variable.
Items collections ofHttpContext
is andIDictionary
key-value collections and that are shared across a singleHTTPRequest
. Yes,HttpContext.Current.Items
is valid for asingle HTTPRequest
. Once after processing, server information is sent back to the browser, the variables that were set in theItems[]
collection will be lost. Whereas forSession
variable, the information is valid for multiple requests as this is user specific. Thesession
variable only expires either on Session Time Out or explicitly clears the values.
Let’s have a quick look at how we can store information inHttpContext.Current.Items
:
HttpContext.Current.Items["ModuleInfo"] = "Custom Module Info”
And retrieve it like:
string contextData = (string)(HttpContext.Current.Items["ModuleInfo"]);
As I said,HttpContext.Current.Items
stores data for a very limited time period, then when can we use this? Yes, this is extremely useful when we want to share content betweenHttpModule
andHTTPHandler
.
Because each and every client request passes through theHTTP PipelineandHTTP Pipeline consistsofHTTP ModuleandHTTP Handler. So If you are writing one custom HTTP Module by ImplementingIHttpModule
and you want pass some information from this module to the current requested page or any other module, you can use theHttpContext.Current.Items
to store the data.
Similarly, you useHTTPContext
Items collection when you are sharing the same information across the different instance based on the user request and that request could be changed for a different request.
While using Context Items collections you need to keep one things that,Items collections holds the objects, so you need to do propertype casting whileretrieving it.
To summarize, in ASP.NETHttpContext.Current.Items
allows us to hold informationfor a single request. We can use it to store short term information. Storing such kind of information is extremely helpful to send information across different custom modules or to requested pages. You have to make sure that the data you are using inHttpContext.Current.Itemsis only valid for that current request and data should be flashed out automatically when request is sent to a browser for any new request you have to store the data again. Whereas session variable is valid for every request unlesssession
timeout is not reached or we explicitly clear the session.