Session problem

[Igor]

I use session variables for login and some little data, but session time out
will be 2-3 hours. If I have lot of visitors with long session time, can I
be in trouble (or my server). Is it dangerous or to hard for server or
session is only on the client machine?

 

[nahid]

I use session variables for login and some little data, but session time out
will be 2-3 hours. If I have lot of visitors with long session time, can I
be in trouble (or my server). Is it dangerous or to hard for server or
session is only on the client machine?

hi,
no session always keep in server side.
if you thing lots hit increase lots memory in server side you can also
save session in database

check it out for more detain ls
http://idunno.org/articles/277.aspx

but its seems it you store Little data in session and your server has
a good configuration may not need to go in hardcore way.

hope help...

nahid
http://nahidulkibria.blogspot.com/
http://www.kaz.com.bd

 

[Igor]

check it out for more detain ls

http://idunno.org/articles/277.aspx

but its seems it you store Little data in session and your server has
a good configuration may not need to go in hardcore way.

It is data like LoginName and memberEmail. It is arround 20 bytes per 1
user. Would be a problem if I have cca 10000 users per day and session
timeout is 5 hours?

 

[Peter Bradley]

Why would a user not interact with the application for five hours and still
expect the Session to be running?

As I understand it, the session is renewed on every postback.


Peter

 

[Mark Rae [MVP]]

It is data like LoginName and memberEmail. It is arround 20 bytes per 1
user. Would be a problem if I have cca 10000 users per day

I wouldn't have thought so. However, when calculating server load, you
really need to be thinking about the maximum number of *concurrent* users...

and session timeout is 5 hours?

Is there any reason that you have such a huge session timeout, especially
when the session contains login details...?

Seems a bit of a security risk to me...