Open GoogleCodeExporter opened 9 years ago
Original comment by limpbizkit
on 1 Jun 2008 at 7:35
Original comment by sberlin
on 22 Feb 2011 at 1:53
[deleted comment]
Not sure how to handle this sort of thing yet - on one hand, we might want to
enable stronger logging, but only if we can make sure we're not penalizing
performance. This almost feels like it's not looking for logging as much as a
facility to query the bindings at run-time and get information out of them.
This is possible with the SPI, and may be a nice extension.
Original comment by christia...@gmail.com
on 4 Jun 2012 at 6:02
While we might want to add some more articulated logging (Want to wait and look
at performance-neutral loggers), you can do this with the SPI (provision
listener), so I'm going to close this.
Original comment by cgruber@google.com
on 18 Nov 2013 at 7:58
Original issue reported on code.google.com by
robbie.v...@gmail.com
on 9 Aug 2007 at 6:33