You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-user@logging.apache.org by Lachlan McCabe <La...@apm.com.au> on 2007/04/27 02:19:18 UTC

Website content errors/ambiguity

Hi,


I've found this comment on your website that is confusing to me.


 


On http://logging.apache.org/log4net/release/features.html#context, the
text "is can" makes it contradictory, which one is it?


 


"Logging Context


log4net can collect logging context data in a way that is transparent to
the developer at the point of logging. The GlobalContext and the
ThreadContext allow the application to capture contextual data and for
it to be attached to logging messages. For instance, in a web service,
once the caller is authenticated the username of the caller is can be
stored in a ThreadContext property. This property is then automatically
logged as part of each logging message."


 


Also on http://logging.apache.org/log4net/release/faq.html, the
Framework Support link does not work.

 


"What are the prerequisites for log4net?


log4net runs on many different frameworks and each framework has its own
requirements. As a rule of thumb you will need an ECMA-335 compliant CLI
runtime, for example, the Microsoft .NET runtime 1.0 (1.0.3705) or 1.1
(1.1.4322). 

Not all frameworks are created equal and some features have been
excluded from some of the builds. See the Framework Support
<http://logging.apache.org/log4net/framework-support.html>  document for
more information."

 

Thanks


Lachlan


RE: Website content errors/ambiguity

Posted by Nicko Cadell <ni...@neoworks.com>.
Thanks for the heads up. I have updated the site.

 

The new text for the Logging Context section is:

 

log4net can be used to collect logging context data in a way that is
transparent 

to the developer at the point of logging. The GlobalContext and the 

ThreadContext allow the application to store contextual data that is

attached to logging messages. For instance, in a web service, 

once the caller is authenticated the username of the caller could be 

stored in a ThreadContext property. This property would then be
automatically 

logged as part of each subsequent logging message made from the same
thread.

 

Thanks,

Nicko

 

------------
nicko cadell <ni...@neoworks.com>
+44 (0)20 7025 0933
http://www.neoworks.com/
software consultancy.solutions.support 

From: Lachlan McCabe [mailto:Lachlan.McCabe@apm.com.au] 
Sent: 27 April 2007 01:19
To: log4net-user@logging.apache.org
Subject: Website content errors/ambiguity

 


Hi,


I've found this comment on your website that is confusing to me.


 


On http://logging.apache.org/log4net/release/features.html#context, the
text "is can" makes it contradictory, which one is it?


 


"Logging Context


log4net can collect logging context data in a way that is transparent to
the developer at the point of logging. The GlobalContext and the
ThreadContext allow the application to capture contextual data and for
it to be attached to logging messages. For instance, in a web service,
once the caller is authenticated the username of the caller is can be
stored in a ThreadContext property. This property is then automatically
logged as part of each logging message."


 


Also on http://logging.apache.org/log4net/release/faq.html, the
Framework Support link does not work.

 


"What are the prerequisites for log4net?


log4net runs on many different frameworks and each framework has its own
requirements. As a rule of thumb you will need an ECMA-335 compliant CLI
runtime, for example, the Microsoft .NET runtime 1.0 (1.0.3705) or 1.1
(1.1.4322). 

Not all frameworks are created equal and some features have been
excluded from some of the builds. See the Framework Support
<http://logging.apache.org/log4net/framework-support.html>  document for
more information."

 

Thanks


Lachlan