On Mon, 12 Jun 2006 [EMAIL PROTECTED] wrote: > I have given this more thought. The point is to create an API that can be > used in prototyping for the purpose of logging. Doesn't matter what code > sits behind it. The API either meets the requirements or it doesn't. If > we have done a good job with the API, we can swap out the code behind it > with no effect on the application.
I agree with this approach. Since there may be some configuration issues remaining with syslog-ng, a simpler interface will be easier replace than one specific to syslog should that be necessary. Further down the road, if/when we use a general messaging framework, a simpler api wil make the transition easier and allows us to swap earlier and support our existing code. cheers, Ray _______________________________________________ LSST-data mailing list [email protected] http://www.lsstmail.org/mailman/listinfo/lsst-data
