Actually, I was thinking more of
1. check for existing logger ( message.loc1)
If (!exists)
create new logger
2. add appender
3 log messages
4 destroy appender
5 release logger.
I'm not sure why that is such bad design. (I only have a few years
programming and self taught).
So, given that
Hi
One of the basic log4net things is the named logger. If you are using
the same loggername, you will allways work on the same instance of the
logger. If you configured a named logger once, you do not need to do
this again. The repository stores the reference to the once configured
logger.
I gue
As I am trying to work on this project, I am realizing I need to provide
more info.
The project is a web service that recieves data from 120
locations simultaneously. The problem I have is that all the data gets
lumped into 3 primary logfiles. There are 10 threads handling data from
these various
