Using Profile for session state

  • Thread starter Thread starter milop
  • Start date Start date
M

milop

Hello.

Not wanting to have to cast every object that needs to be stored in session
state, I am thinking of using Profiles introduced with ASP.Net 2.0.

All of my objects are serializable so that's not an issue.

My main concern is persistence: I don't need to persist this information
beyond the session. So perhaps in the Session_End event in the Global.aspx
file can take care of deleting it.

Has anyone utilized Profiles to achieve strong-typed session state? What are
the pitfalls?

Any and all comments are much appreciated.

Thanks in advance,

Mike
 
Hi, Patrice.

I appreciate the suggestion, and did see that code, but I'm not crazy about
it. Profiles do all this work behind the scenes, but I am concerned about
side effects (things I haven't thought about yet) that may exist when using
Profiles as a session state mechanism.

Thanks again,

Mike
 
there is nothing wrong with this approach. you should turn session off, as
you don't need the resource.

the only downside is security, but no different than non-expiring sessions.
just take care with privacy data.


-- bruce (sqlwork.com)
 
Back
Top