Good to hear from you David!
These are good points - any more detail we can squeeze out
before the
event would be good.
Estacado's commercialized version of repro uses log4cplus
(similar to
log4cxx). The ExternalLogger
is a fairly reasonable interface for allowing you to plug
anything
you want in to capture the existing
logging inside resip. What we should do is talk about a
common
interface we can use that would allow
attachment of whatever backend logging system makes sense
for an
environment, and make sure
that interface allows you to make the kind of rich logging
statements
you can make in the log4* world.
We've also adapted to many database systems for things like
registration stores (and other
bits of information you might use as part of admission
policy,
message adornment, or routing
decisions). There's no need to hardcode repro to any one of
these,
the flexibility of the monkeychains
makes attaching to whatever you need to fairly
straightforward. Are
you proposing teaching
the default monkeychain to talk to DTL, or just having a
monkey that
can use DTL in the codebase?
RjS
On Jan 17, 2006, at 6:36 AM, David Schwartz wrote:
> Hi Robert.
>
> From our experience at Kayote for any server to achieve
"production
> grade" there must be strong logging and database
capabilities. The
> tools/technologies we use in our network to achieve
these goals are
> log4cxx and DTL respectively. We have written wrappers
around these
> and would be happy to share them with the community.
>
> Whether or not these are chosen the point I wish to
raise is that
> it is imperative that repro address these issues sooner
rather than
> later.
>
> Cheers,
>
> David Schwartz
>
> -----Original Message-----
> From: repro-devel-bounces list.sipfoundry.org
[mailto:repro-devel-
> bounceslist.sipfoundry.org] On Behalf Of Robert Sparks
> Sent: ג 17 ינואר 2006 05:01
> To: Scott Lawrence
> Cc: Repro Developers
> Subject: Re: [repro-devel] Coding party Feb 16-18 BOS
>
>
> On Jan 16, 2006, at 8:00 AM, Scott Lawrence wrote:
>
>> If there are other goals that you have and would
like to get added to
>> the list, I suggest you send them directly to me
and I will try to
>> put
>> together a combined list.
>
> Actually, this should be part of a bigger conversation.
>
> Please send all requests for enhancements to repro to
the list. If
> you think its something we should spend time on during
this coding
> session, include an argument for why it should be
addressed earlier
> rather than later. Having this in the archives will
help with
> planning future sessions (and allow individual
contributors to
> focus work on areas that will help the largest
audience).
>
> Thanks,
>
> RjS
> _______________________________________________
> repro-devel mailing list
> repro-devellist.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/repro-devel
_______________________________________________
repro-devel mailing list
repro-devellist.sipfoundry.org
https://list.sipfoundry.org/mailman/listinfo/repro-devel
|