While reading on ASP.NET Core Session, and analyzing the difference with previous version of ASP.NET we bumped into a problem...
At Managing Application State
Session is non-locking, so if two requests both attempt to modify the contents of session, the last one will win. Further, Session is implemented as a coherent session, which means that all of the contents are stored together. This means that if two requests are modifying different parts of the session (different keys), they may still impact each other.
This is different from previous versions of ASP.NET where session was blocking, which meant that if you had multiple concurrent requests to the session, then all requests were synchronized. So, you could keep consistent state.
In ASP.NET Core you have no built-in means to keep a consistent state of the session. Even assurances that the session is coherent does not help in any way.
You options are:
a@href@title, b, blockquote@cite, em, i, strike, strong, sub, super, u