HttpContext.Items vs Session
Join the DZone community and get the full member experience.Join For Free
Since .NET first because available, passing data around during a request has become a lot easier. The ability to set a property has made that so. Still there are times when setting a property just won’t do the trick.
One such time is getting data from the middle tier back up to the view separate from a DataBinding operation. That is, you databind a control to the middle tier and that method needs to set a value that will be used elsewhere in the view. Not in the item that is being bound.
The natural, obvious, tendency is to set a session variable. But, there is a better way.
The problem with session variables is that they have to be cleaned up manually or they will hang around longer than we actually need them. This will use up more session memory than is required and can potentially cause side effects that will be difficult to debug.
Instead you can use the Items collection that is part of the HttpContext class. It works the same as a session variable, but it only hangs around for the duration of the request. Once the information is sent back to the browser, the variables that were set in the Items collection go away.
You might set your variable in the middle tier like this:
HttpContext.Current.Items["myVar"] = "Some Data Here";
And retrieve it later like this:
string myVar = (string)(HttpContext.Current.Items["myVar"]);
Published at DZone with permission of Dave Bush, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
The SPACE Framework for Developer Productivity
Mastering Go-Templates in Ansible With Jinja2
Event-Driven Architecture Using Serverless Technologies
Using Render Log Streams to Log to Papertrail