Send reply to: "LOG4J Developers Mailing List" <log4j-
[EMAIL PROTECTED]>
Date sent: Thu, 23 Aug 2001 00:56:41 +0200
To: [EMAIL PROTECTED]
From: Ceki G�lc� <[EMAIL PROTECTED]>
Subject: Revised log4j interfaces
Copies to: [EMAIL PROTECTED], [EMAIL PROTECTED]
> I have just started working on a revised log4j interface. An *early*
> draft of the proposal is available at:
>
> http://jakarta.apache.org/log4j/docs/proposal.html
>
> Your input is most welcome.
>
>
> --
> Ceki G�lc� - http://qos.ch
Regarding internationalisation, IMHO it is desirable to be able to
defer object + parameter formatting to a server side context, or
even to store the object + parameters (+ resource context name) in
a database, to provide formatting in a different locale from the
original client locale. This would require extending the API to
provide the parameter and resource context information.
If the object or any of the parameters do not implement
Serializable, and the appender (or equivalent logging destination)
uses serialisation to transport objects to a remote server, the
appender mighthave to fall back to formatting the object +
parameters as a string.and send the string to the server. I think it
would be best to leave this decision up to the appender, since it
may use an alternative marshalling which does not involve
serialisation.
--
Andrew Harris
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
