[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: question % logging
At 17:34 12/06/2001 +0200, you wrote:
>Hello!
>
> >> >in case, if some more advanced logging is needed, log4j can be used.
> it can be
> >> >found at http://jakarta.apache.org
> >
> > ozone already uses Log4J. Still the question is, is it a good idea to make
> > it part of the ozone _API_? (especially since there are other log
> > solutions/standards/things are waiting around the corner)
>
>i think there 2 different types of logging - Ozone's internal logging and
>user application
>level logging. these 2 types shouldn't be mixed. first type just records
>events which are
>related to Ozone operation (like user login/log out, server events or
>problems, etc). second
>type is related to busness logic which is implemented by particular user.
>i would suggest
>not to expose any kind of internal logging API to user level. it should be up
>to user how to log it's events. and it's not a database responsibility to
>care about such
>logging.
I think that, for good performance reason, and to allow asynchronous and
modular logging, as your Database can be
see as some sort of application server, it makes some sense to expose a
business-logic logging API.
Am I wrong?
>/AAV
>
>----------------------------------
>E-Mail: Aleksey Aristov <aav@morgana.de>
>Date: 12-Jun-2001
>Time: 17:24:31
>
>This message was sent by XFMail
>----------------------------------