So this routine's code has for example: HttpContext.Current.User, which is request safe and thread safe by default. It then pulls a value from the service. This value is stored in the thread's local stackframe, so every thread has a different instance of that value. It then returns that value, so it's perfectly threadsafe.
That's ok for LoadCurrentUser() body but how can we be sure the code it calls is thread safe too? I meant, proven that, for example, HttpContext.Current.User is thread safe, what about GetSiteUserByUid()? We don't know anything about its thread safety. Couldn't it potentially be thread unsafe thus making the whole method thread unsafe?
Thanks. -- Efran Cobisi http://www.cobisi.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
