Frank Schönheit wrote:
I'd like to propose a new logging API, which is modeled after the Java logging API (though not (yet) as powerful).
[...]
Feedback to this proposed API is highly welcome.
Sorry this feedback is rather late. Anyway, I am completely confused by what you propose. How is client code supposed to obtain an appropriate logger? Is there a globally managed set of loggers from which clients can choose? (For example, I would assume Java's static Logger.getLogger to map to a UNO service constructor, or a method at an XLogManager interface, but not a method at the XLogger interface.) Excessive calls to XLogger.logp are potentially expensive in every scenario, not merely remotely (three strings are marshalled that are potentially not needed when the given logging level is too fine). How exactly are LoggingRemote and XLoggingRemote supposed to help here? Please elaborate.
(Also, Java has Levels as a fixed enum, not an open set of integers. Why deviate from that? Do you think there ever will be need for more levels than the given seven?)
-Stephan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
