title: N-tier architecture with WCF and ASP.NET session state problem
body: <p>I'm developing one of my personal projects and I found some problem.</p>
  
  <p>It's an n-tier architecture:</p>
  
  <ul>
  <li>Framework.</li>
  <li>WCF Framework service.</li>
  <li>ASP.NET control that connects to the WCF Framework services in the server-side.</li>
  <li>ASP.NET client hosting that control.</li>
  </ul>
  
  <p>WCF service is in ASP.NET compatibility mode.</p>
  
  <p>What's the problem? Each request is in a different session. I found that because stored values for sessions are reseted in each request, as I stated before.</p>
  
  <p>I've two questions then:</p>
  
  <p>1) - Someway obvious but I want a confirmation - Does the fact of calling WCF Framework services in server-side mean that the session is for the server and not per client? </p>
  
  <p>2) Is first question fact the reason of getting a new session after each request?</p>
  
  <p>In the end, I'm about of disabling ASP.NET compatibility mode for that WCF Framework service and develop my own session state management, which isn't a hard task, but I'm not a friend of reinventing wheels.</p>
  
  <p>Thank you in advance.</p>