logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Moore <jim.mo...@veritas.com>
Subject RE: Cross-language logging possibilities with log4j - Summary and next steps
Date Thu, 15 May 2003 18:05:06 GMT
"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?"

Both "guaranteed" and "non-guaranteed" delivery (specifically "RPC" and
"messaging") should be available, though that does not mean that both would
need to be delivered at the same time.  If RPC, for example, is released
first, that would be fine as long as provision is made for RPC.  SOAP, while
it may be too heavy for this kind of thing, can provide a model on how that
can be done.


-----Original Message-----
From: Mahurkar, Anup [mailto:amahurka@tigr.org] 
Sent: Thursday, May 15, 2003 1:27 PM
To: 'Log4J Developers List'
Subject: 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


Mime
View raw message