Hi people! Thanks, Philip!
About: > I guess this comes back then to CallContext in System.Remoting.Messaging. It > appears that this is actually what asp.net uses to do it's httpcontext. There > was just the "thread" about that with terms of abuse thrown around ;-) You can check: http://authors.aspalliance.com/bbilbro/viewarticle.aspx?paged_article_id=5 to a inner study of HttpContext.Current, and an implementation of a similar Context. Apparently the HttpContext.Current uses the Remoting CallContext. 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. Ergo, a ThreadStatic variable setting, for example, in BeginRequest, MUST BE ONLY for my thread, until EndRequest. And then, is safe for me. But, in my original post, I refer an article that (apparently) states that it is not the case.... ???? Someone that think like me: http://weblogs.asp.net/yreynhout/archive/2003/03/19/4061.aspx I ask: any official documentation that clarifies the point? Angel "Java" Lopez http://www.ajlopez.com/ =================================== 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
