Open GoogleCodeExporter opened 8 years ago
Please Explain it in detail, How asynchronous logging is used in internal code.
Original comment by s.raj0...@gmail.com
on 29 Sep 2010 at 6:49
Let me add my $.02, as I would love to see this feature as well. The idea is to
off-load most of the work related to logging to a separate thread. This is to
allow for faster event handling in real-time-ish systems.
In great simplification, the log statement should just add a message to a queue
or the like. The queue should be processed by a separate, lower prio thread,
which does the actual logging.
Please do not forget about some mechanism to drop logging messages when the
queue overflows, to avoid memory exhaustion.
Original comment by pawel....@gmail.com
on 29 Sep 2010 at 12:43
I'm very interested in this as well. Is this in progress or what's the status?
I would love it in glog or I've to carve it out myself ;-)
Original comment by kjell.he...@gmail.com
on 16 Dec 2010 at 7:58
Any update on this guys? Thanks.
Original comment by rpope...@gmail.com
on 27 Jun 2013 at 1:35
was this implemented in the latest release?
Original comment by hatem.taleb
on 28 Aug 2013 at 8:16
What is the status now?
Original comment by daibi...@gmail.com
on 24 Sep 2013 at 8:29
Original issue reported on code.google.com by
shinichi...@gmail.com
on 1 Jul 2010 at 7:08