title: ASP.Net Session.Timeout - Is StateServer and Programmatic Session.Timeout Good Enough?
body: <p>Reading around, it looks like changing asp.net session time when using the InProc model requires two changes...</p>
  
  <ol>
  <li>web.config -  Application Pool Idle</li>
  <li>Timeout - Seems you should set this >= Session.Timeout</li>
  </ol>
  
  <p>I gathered this from reading <a href="http://asp-net.vexedlogic.com/2012/05/23/aspasp-net-session-timeout-how-do-i-change-it/" rel="nofollow">http://asp-net.vexedlogic.com/2012/05/23/aspasp-net-session-timeout-how-do-i-change-it/</a>.</p>
  
  <p>So, if I don't have the luxury of changing timeouts on application pools, I'm wondering if I change  to use StateServer and then programmatically set Session.Timeout as described in the article above, do I need to worry about what web.config @timeout and application pool idle settings are set at?  Will my two actions take care of everything?</p>
  
  <p>If it does take care of it, I guess the next question is whether or not anyone knows how performance compares from InProc vs StateServer.</p>
  
  <p>Thanks in advance.</p>