> But then: I think that HttpContext.Current works during the life of a > request, and THEN, the thread during the life of a request, MUST BE the > same. The thread is associated to a context, and then, It cannot be used on > another context DURING THE LIFE of the request.
If MS regards this as an implementation detail, we may never know for sure, but I would also love to have this clarified. Do I get my thread exclusively during my request? According to J.Merrill's response the answer is no. But then since CallContext is a smaller unit than thread, and because asp.net itself uses this, perhaps this mechanism is OK. ===== Philip - http://blogs.xcskiwinn.org/panmanphil "There's a difference between righteous anger and just being crabby" - Barbara =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
