J
jensen bredal
I need to keep track on user "session data" while still turning session off
as
i do not want users login to expire?
Thanks
JB
as
i do not want users login to expire?
Thanks
JB
mortb said:You could store this information in a cookie written to the user's
browser.
If there is much data to be stored you'd store some key in the cookie and
the rest in a database mapped to the key.
hope this helps,
mortb
Sessions time out. Each Session has a certain amount of memory overhead
associated with it. If Sessions never time out, you've created a custom
Memory Leak in your app. Every time a Session is initiated, it adds to the
memory overhead. And with no way to remove a Session, the memory overhead
keeps building until your system is out of memory.
The reason that Sessions time out is that HTTP is stateless. Each Request
happens "in a vacuum" so to speak. The server has no way of knowing
whether or not the client is even there until it receives a Request.
SessionState was created to emulate statefullness for a given client. It
(generally, by default) creates a Session cookie on the client, which is
sent with each Request, identifying the Session (Memory block) that
belongs to that client. Once the client stops sending Requests, the
Session kills itself after the Timeout interval. The lack of Requests is
the only way the server-side app can know that the client has "gone away"
so to speak.
Well i do refresh before the session is set to expire but, that does not
stop i from expiring.
What i'm i doing wrong?
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.