On 10/25/07, Michael Schall <[EMAIL PROTECTED]> wrote:
> We wrap log4net and have had no issues and we have a logger for each class.
> I have not swapped it out as your argument suggests, but I don't like to use
> any library directly. It shields you not only from swapping out a library,
> but fro
t; make it down the road … they all keep getting rewritten or close to it as
> new technologies keep arriving … so log4net being the best-in-breed I say
> use it ….
>
>
>
> owen
>
>
> ----------
>
> *From:* Peter Drier [mailto:[EMAIL PROTECTED]
> *Se
est-in-breed I say use it
owen
From: Peter Drier [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 24, 2007 9:05 AM
To: Log4NET User
Subject: Re: Newbie: Log4Net or MS Logging Application Block?
I've seen many people wrap log4net just so they co
I've seen many people wrap log4net just so they could swap it out down the
road..
Doing that, you lose the context sensitivity of having a logger in each
class.. one of log4net's greatest strengths..
And I've never ever seen it actually replaced down the road.. It makes much
more sense to creat
Hi,
it was just my back of the envelope guess at total working set usage
when I was considering the one-static-logger-per-code-class approach,
which was new to me at the time.
this was my thinking...
10K code classes is definitely an upper limit, and 100-1000 is probably
the common range. I
I worked at a financial firm a few years back before the Logging Application
Block existed.. Microsoft came to us and asked us what we wanted next from
them in the area of Application Blocks.. Logging was one of the choices in
their potential near term plans..
Everyone in the room, including tho
> I personally have my own wrapper object that includes a Logger
instance and I create a
>static one of those per code class. I am budgeting about 100bytes per
instance at, say,
>10K classes max for 1MB working set usage. I'm not sure if this is
accurate.
I assume you mean 10K instances, n
José Joye wrote:
>
> However. in order not to be too hardly tight to log4net, we decided
> to build a facade to abstract the Logging framework. This was done in
> order to easily switch the logging framework we use behind the
> scene.
>
> José
>
Thanks Jose, I had already decided to take
ewbie: Log4Net or MS Logging Application Block?
Thanks Mike, thats some good info.
I am going to knock up proof of concepts using both frameworks and
see what
I get...
--
View this message in context: http://www.nabble.com/Newbie%3A-
Log4Net-or-MS-Logging-Application-Block--tf4669838.html#a13359569
Thanks Mike, thats some good info.
I am going to knock up proof of concepts using both frameworks and see what
I get...
--
View this message in context:
http://www.nabble.com/Newbie%3A-Log4Net-or-MS-Logging-Application-Block--tf4669838.html#a13359569
Sent from the Log4net - Users mailing list
I am not a log4net expert... so please consult others too and do your
own investigation.
:: Category vs. log4net filtering
- Category is a flat filter rule. log4net hierarchy is much more
powerful. for additional filtering on other attributes, add info to
the properties and/or stacks and fil
OK, that very good information.
I see that the MS Logging Application Block (LAB) allows messages to be
routed based on "Category" and each message contains a collection of
name-value pairs of meta data.
What is the corresponding Log4Net technology? From what little I have seen,
messages are rou
For my purposes, Log4net is better in every respect. I wish I knew this
two years ago.
I am the architect for a medium-sized distributed project that is
perhaps in the 200-300K lines category. We started with EntLib logging
but never really enjoyed it - the configs and the lack of built-in
> Audit will require transactions, which is to say that the calling code
needs
>to know if the Audit message has been persisted or not before it can
>continue.
>From the log4net FAQ on the Apache site:
"Is log4net a reliable logging system?"
"No. log4net is not reliable. It is a best-effort and fa
14 matches
Mail list logo