You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Mahurkar, Anup" <am...@tigr.org> on 2003/05/15 19:26:45 UTC
RE: Cross-language logging possibilities with log4j - Summary and
next steps
Based on the discussion so far I gather that:
a) There is definitely interest in cross-language logging using XML as the
data exchange mechanism
b) There are concerns about using SOAP/XML-RPC because of the potential
impact on logging performance
c) A fair bit of work has already been done on XML serialization of
LoggingEvent for Chainsaw and could be (re)used
d) It has been suggested that de-serialization should probably rely on SAX
based parsing to get better performance
So the question becomes what next?
1) It seems like there are two possible implementations, one using
SOAP/XML-RPC, or the other using SimpleSocketServer or some derivative of
that class. Any thoughts on which should be taken up first?
2) If the same server is to be used for logging from multiple instances of
an application what would be the most flexible approach to create a separate
context for each instance of the application so that even though the
application uses the same configuration file, the output from different
instances is sent to different directories (FileAppender), or somehow marked
uniquely for other appenders?
3) Can one go with the assumption that logging is not guaranteed, so if the
server cannot keep up with the pace of the requests, some of them may be
dropped?
Anup Mahurkar
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org