O
olrt
I'm still convinced that the behaviour of ASP.NET in respect to code
invoking static members is coherent with the documentation of the
static C# keyword...
By the way, you can also exploit ASP.NET "Application" context object
to store objects that are shared between all users of your Web
application...
But you'll have to ensure that all calls to methods of the object leave
it in a coherent state (that is you'll have to synchronize the threads
that call the methods which affect the state of the object).
I think that's what you did with your static methods...
invoking static members is coherent with the documentation of the
static C# keyword...
By the way, you can also exploit ASP.NET "Application" context object
to store objects that are shared between all users of your Web
application...
But you'll have to ensure that all calls to methods of the object leave
it in a coherent state (that is you'll have to synchronize the threads
that call the methods which affect the state of the object).
I think that's what you did with your static methods...