Pergunta

After a previous post about an issue with Session State being locked on every request (normal behavior for Asp.Net), tried fully disabling Session State (). This, in fact, disables the Session object and throws exceptions if try to use it. However, as stated in the named post, all requests are still serviced in a serialized fashion. This is, a second "simultaneous" request doesn't get served till previous gets finished served. Related documentation states that disabling Session State avoids the lock in the session but, in my case, my requests are still serviced serially.

This is not MVC.

This is my previous post Custom handler processes multiple requests serially and not simultaneouslly

Any help would be appreciated.

Foi útil?

Solução

Turns out this always happens inside the developer environment (cassini). When dissabling session state there is no possible access to the Session object but it seems to exists a lock request somewhere.

Debugging in IIS this doesn't happen.

Hope this help.

Licenciado em: CC-BY-SA com atribuição
Não afiliado a StackOverflow
scroll top