hmmm... my first instinct was to reply that a static member is actually
instantiated for each session, since each session is sort-of like its
own application.
Then I realized I wasn't clear on this topic and tried to find an
answer.
Failed to do so, but found an example of how you can avoid problems by
wrapping your access to static members in a lock statement.
See here:
http://www.developerfusion.com/show/3821/5/
and, now that you put the bug in my ear, I'll have to find out what's
the real scope of a static member, so maybe I'll post again when I'll
find a better answer.
F.O.R.