Why a Logging Framework Should Not Log

Re:Why a Logging Framework Should Not Log by marcosdumay on Friday May 06, 2016 @01:33PM (#11645413)

Yes, if you created a framework, that will call your code, yes, it can log. It can also provide a logger implementation, or request one from you, whatever it deems better, and your code must comply.

But a library, that your code will call, must not log. Ever. That includes any portion of a framework that you have to call, but it using services upper on the stack can make this rule hard to see. It must not include a logger implementation, and not call any global logger supplied from you.

It seems we are arguing over the definition of those two cases.

[ Parent | on HN ]

Re:Why a Logging Framework Should Not Log by empthought on Friday May 06, 2016 @01:45PM (#11645485)

So in the case of Apache HTTPClient (which I would call a library), are you saying that it is a design flaw that it provides logging statements of its internals, when provided the proper configuration/logging implementation?

If so, I would have to disagree based on pragmatic grounds, unless you have another credible way to acquire the information present in http wire logging or connection pool events, for example.

[ Parent | on HN ]