RE: [reSIProcate] external logger
I think that's great as no doubt everyone will likely be integrating this
into larger schemes and quite often have their own logging code.
-Tom
thomasgal@xxxxxxxxxxxx
> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On
> Behalf Of Justin Matthews
> Sent: Wednesday, January 19, 2005 7:15 PM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [reSIProcate] external logger
>
> Hello,
>
> The application that I am working on that uses resip has its
> own logging functionality. The logger in our app ("myapp")
> has some enhanced features similar to those found in log4j
> (logging configurable using a config file, different outputs
> including sockets, syslog, rolling file appenders...).
> What I would like is for myapp to be in total control of the
> logging. I have modified resip by adding a new
> Log::initialize() function that takes a pointer to a function
> as the only argument and modified Logger.hxx to forward all
> log requests to this function if the external function
> pointer "type" logger is enabled. Is this, or a similar
> solution, something that would be considered for addition
> into resip? Does anyone have any other suggestions for
> adding this functionality?
>
> Thanks,
>
> Justin
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>