Thx for you reply. I think I don't have such a problem understanding static variables. The thing that surpised me the most was the following behaviour and my current understanding of browser requests and how you can pass values among them.
Up until now, I thought that the state of web application was maintained via "sessions/viewstate" and that each request starts with a clean sheet and only later on it's values are recovered from "sessions".
But here, the fact that values initialized when broswer A requested a module are available to requests from other browsers suggests, that the module class stays alive on the server with its static variables setup from the first visit and that subsequent requests from different browsers on different computers accessing the module can read/write to these variables. In fact, I find it extemely handy.
I'll have to simulate a situation when two requests come at the same time though, because I don't know if in that case the value would stay the same for one browser...or if and that will be the case, I think, It can changed during the life cycle of its response.
The question is when is it freed from memory all together?
If interested, I willsend you the visual studio project sample file so that you see what I mean.
Thx again for your reply.