Is it right to used Session to stored the user info?

[Benny Ng]

Hi,all,
In the traditional ASP development.We usually used Session to stored the
user info(user name,user type,etc.). And in the .NET development. We perfer
to used Session or Cache to stored it?
And some articles prompted that this two methods also can solved
that.But i really don't know which is the best choice for my application
development.
And an application block that named "Cache Application Block" is
launched in the Enterprise Library. Is it same as the Cache Object in the
..NET platform? It just a encapsulated?

Any suggestion for this are appreciated.

Thank you.

Benny Ng

 

[Robbe Morris [C# MVP]]

Session is fine for typical "value" types. You can
set a class to use the ISerialize attribute and store it
in session as well.

This really only works well in a single web server
environment. For farms, I like the ScaleOut StateServer
product.

http://www.eggheadcafe.com/articles/scaleout_server.asp

 

[Benny Ng]

Thank you. Then i goto checkout that article. Goto study.

Benny Ng

 

[Hans Kesting]

Hi,all,
In the traditional ASP development.We usually used Session to
stored the user info(user name,user type,etc.). And in the .NET
development. We perfer to used Session or Cache to stored it?

Session by all means. This is user-specific, where Cache is shared
between all sessions. If you store user-info in Cache, then all users
would use the same user-data.

Note: In classic ASP you would (or at least: I would ) store separate
strings and other values. In ASP.Net you could also store some "UserObject"
containing all values for this user under a single Session-key.

Hans Kesting