I think I have found the problem. In my base class I had some variabled declared as "Protected Shared ".
Multiple client sessions would create instances of classes derived from this base class and assign values to the variables (via exposed public properties). There was a situation yesterday where this create/use/destory occurred for two clients within 100ms of each other and caused unexpected results, client B was showing client A's data. I've changed the variable declaration to "Public" and ran a test (making use of System.Threading.Thread.Sleep) and with the Shared declaration I was able to mimic the behavior and with Public it seems to be "thread safe". Is there anything else I should be watching out for with regards to thread safety in ASP.NET - I've been reading up about Singletons but I'm not really sure if I'm on the righ track. Ben On 2/27/07, Ben Joyce <[EMAIL PROTECTED]> wrote:
No worries Erik, I do appreciate yours and anyone's input. If this *is* on-topic on an 'advanced' list as this then I hope someone may have some ideas. Cheers, Ben On 2/27/07, Stoyan Damov <[EMAIL PROTECTED]> wrote: > On 2/27/07, Erik M. Erikson <[EMAIL PROTECTED]> wrote: > > ... > > No offense here. I didn't know you actually helped Ben before you > ruled out his post as off-topic. > > Sorry, > Stoyan > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at http://discuss.develop.com >
=================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
