Why Should You Wrap Your ASP.NET Session Object

home
architecture
view story

24 Kicks

Why Should You Wrap Your ASP.NET Session Object (dev102.com)

submitted by razamit(4545) 3 years, 9 months ago

ASP.NET provides mechanisms for storing information for a single user session or across multiple sessions. This is done using the HttpSessionState and HttpApplicationState classes. The Page class has Application and Session attributes to provide access to current objects. The simple way to access them is as following:

3 comments |category: Architecture |Views: 72
Tweet

tags: Architecture ASP.NET another

Everyones tags:

Your Tags:

Please login or signup.

Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

"Kick It" text
"Kick It" background
kick count text
kick count background
border

Simply copy and paste this HTML into your blog post.

Users who kicked this story:

antny(55) -

hgupta(0) -

ksh2dotnetkicks(135) -

adminjew(1490)

More who kicked this story...

Comments:

posted by xtremebiz(575) 3 years, 9 months ago 0

check this out as well guys - http://codeforeternity.com/blogs/technology/archive/2007/12/19/handling-asp-net-session-variables-efficiently.aspx

posted by senfo(881) 3 years, 9 months ago 0

Maybe I'm just being anal, but I feel like the properties should be in a separate class than the methods. To me, SessionWrapper is the implementation while the properties really have no part of it, which would mean that the properties have no business being there.

Just my humble opinion. Overall, I have no major gripes about the implementation.

posted by lcorneliussen(490) 3 years, 8 months ago 0

Your'e writing "why", so I wrote "how" :D

http://startbigthinksmall.wordpress.com/2008/05/14/how-to-wrap-the-aspnet-session-state/

Most Active Users

What's this?