title: ASP Net Core 3 Session (state) concurrency and integrity
body: <p>I have a page which requests multiple requests concurrently. So those requests are in the very same session. For accessing the session I use everywhere <code>IHttpContextAccessor</code>.</p>
  
  <p>My problem is that regardless of the timing, some request does not see other requests already set session state, instead sees some previous state. (again in timing, the set state operation happened already, still)</p>
  
  <p>As far as I know each requests has its own copy of the state, which is written back... (well "when"?) to the common "one" state. If this "when" is the delayed to when request is completely served, then the scenario what I experiencing is easily happen: The 2nd concurrent request within the session got his copy after the 1st request modified the state but before as it was finished completely.</p>
  
  <p>However this all above means that in case of concurrent request serving within a session there is no way to maintain session integrity. The 2nd not seeing the already done changes by the 1st, will write back something what is not consistent with the already done 1st process change. </p>
  
  <p>Am I missing something?
  Is there any workaround? (with some cost of course)</p>