Using Profile for session state

[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

[=?Utf-8?B?YnJ1Y2UgYmFya2Vy?=]

RE: Using Profile for session state

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)


"milop" wrote:

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
>
>
>