On Mon, Aug 25, 2008 at 3:39 AM, Julien Vermillard
<[EMAIL PROTECTED]>wrote:
> LoggingFilter is a debug tool, in no production application you will
> log all the sent/rcvd message.
>
> The only usage could be exception & connec/disconnet
>
> So I think we could :
>
> hardcode created/sent/rcvd log
Hi,
Julien Vermillard wrote:
Hi,
Comments inline.
On Fri, 22 Aug 2008 22:47:32 +0200
Emmanuel Lecharny <[EMAIL PROTECTED]> wrote:
Hi guys,
I think there is something wrong with the current implementation of
the LogFilter.
Sure it's a bit over complicated, specially that Map for I
I agree: the current LoggingFilter is pretty complicated. I looked at it in
the past but found it too complex to use it.
I even think we could just get rid of it and let our users write a
customized LoggingFilter when they need one.
But what Julien suggest also looks OK to me.
Regards,
Maarten
Hi,
Comments inline.
On Fri, 22 Aug 2008 22:47:32 +0200
Emmanuel Lecharny <[EMAIL PROTECTED]> wrote:
> Hi guys,
>
> I think there is something wrong with the current implementation of
> the LogFilter.
Sure it's a bit over complicated, specially that Map for IoEvent, due
to the fact we aren't a
Hi guys,
I think there is something wrong with the current implementation of the
LogFilter.
The idea is to be able to log something _if_ a specific event is set to
a certain level. For instance, one may log as debug when a
MessageReceived event is received, but only log errors when a
Messag
