N
Natan
Hi.
I use Session to store an "User" object for authentication purposes, and
expose it using a class that make all the necessary tests to know if the
user can access that area.
I know StateServer is slower because of the serialization and in a web
environment, the memory usage grows with the requests. But some people
told me they had problems losing data or iis crashing when storing some
hundred sessions with objects (i`m considering objects that are about 1k
serialized).
Is this right? Are there any problems in using SessionState for those
kind of objects other than memory and serialization?
I use Session to store an "User" object for authentication purposes, and
expose it using a class that make all the necessary tests to know if the
user can access that area.
I know StateServer is slower because of the serialization and in a web
environment, the memory usage grows with the requests. But some people
told me they had problems losing data or iis crashing when storing some
hundred sessions with objects (i`m considering objects that are about 1k
serialized).
Is this right? Are there any problems in using SessionState for those
kind of objects other than memory and serialization?