< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

RE: [reSIProcate] external logger


Oops -- teach me to respond to my mail in received order.

Thanks for the implementation, Justin. I will take a look and propose a way to
generalize the logger shortly.

thanks,
david


Quoting Justin Matthews <justin.matthews@xxxxxxx>:

> Also, here is an example of how I am using this:
> 
> void ResipLogFunction(int resipLevel, const char *subsystem, 
>                                        const char *file, int line,const char
> *message)
> {
>     //translate and send to my apps logging subsystem...
> }
> 
> bool MyClass::Create(void)
> {
>     resip::Log::initialize(ResipLogFunction);
> }
> 
> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Justin
> Matthews
> Sent: Thursday, January 20, 2005 10:29 AM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [reSIProcate] external logger
> 
> Sounds like there is some interest, attached are the files I modified.
> These files are intended to be a starting point.  Since I am a newbie I am
> sure they may be a better/cleaner way of adding this.  
> 
> Thanks,
> 
> -Justin
> 
> -----Original Message-----
> From: Thomas Gal [mailto:ThomasGal@xxxxxxxxxxxx] 
> Sent: Thursday, January 20, 2005 10:08 AM
> To: 'Justin Matthews'; resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: 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
> > 
> 
> 
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>