Guten Tag Alder Netw,
am Dienstag, 13. Mai 2014 um 02:06 schrieben Sie:
> OK, we would love to use the existing Log4cxx buffering mechanism,
> but we found the time-stamp appended by Log4Cxx is the dequeue time
> rather than the enqueue time, so the question becomes is there any
> control over usi
Thanks Thorsten for the prompt reply.
OK, we would love to use the existing Log4cxx buffering mechanism,
but we found the time-stamp appended by Log4Cxx is the dequeue time rather
than the enqueue time, so the question becomes is there any control over
using the original log generating time instea
Guten Tag Alder Netw,
am Montag, 12. Mai 2014 um 20:37 schrieben Sie:
> A question regarding the time-stamp control over the
> log message, can the app provide its own time-stamp?
No, you would need to re-implement the macros LOG4CXX_* you use in
your app, subclass Logger to override forcedLog,
A question regarding the time-stamp control over the
log message, can the app provide its own time-stamp?
This is useful when app buffers a large amount of logs
and wish to preserve the original event generating timestamp.
Thanks,
- Alder
