Quote Originally Posted by AnRoeh View Post
You said the reason is process pooling. Can you give some information about this?
Process pooling means that the WebApp Server starts multiple instances of your webapp.exe when it starts your webapp. When an HTTP request comes in it will be assigned to one of the available processes. It does this regardless from which session the request comes. This means that a process can handle a request from session 1, the next request can be from session 3 and then another request from session 1 can come in. This means that there is no persistent state on the server which is one of the reasons why we invented WebGet and WebSet.