We have created a ASP.NET website to give ticket-based support to our customers. The customer can send queries to us, and they can see replies, if any(we do provide application on customer side to send quires and replies).I am using ASP.net state server sessions in our asp website. Application checks for new replies in database for a duration of 45 minutes.After 45 minutes those sessions are no longer used.If no replies are present then it checks for replies on next day. If customer puts new question then we create new session for it, and old session is no longer used. To check on next day we directly fetch it from our database and show all replies which are not seen. Before I had asked question about loss of session and then I solved it by using asp.net StateServer.
Now I have set session time out to 1440 i.e 24 hours. But we need to check replies for 45 minutes so we can reduce session timeout I think.But to be on safer side we set it to 24 hours.
- Is there any negative effect if I set it to large values?
- Does it effect on my web server performance?
- What is the best approach to set session time-out in my case.