On 2/16/06, Aaron Morton <[EMAIL PROTECTED]> wrote: > Perhaps you could create something similar (add objects to the > GlobalContext) to read values from the HTTPContext as a work around.
Nice - Ok - for the two things I've mentioned so far (User Identity and Requested Url) this would be a fine solution. This allows us to safely capture state about a request. However for business layer logging - where the context is dependant on the actual action performed this does not sound like it would work well. (i.e. the contextual information is dependant on the actual sequence of actions performed with a single request). Thanks for the useful ideas! (They solve my immediate problems). However I still have several problems: 1. ThreadLogicalContext is demonstrably not safe for use in a ASP.NET environment. (Not just in pages but in any components used by those pages). 2. This is not documented or mentioned anywhere. 3. There is no log4net support/recommended alternative (or pattern/best practice). j.
