mongo-ruby-driver/lib/mongo/util
asinbow.wang 56968e8ad3 fix log debug level detect
* reason
  there hardcodes DEBUG_LEVEL in logging.rb:
    DEBUG_LEVEL = defined?(Logger) ? Logger::DEBUG : 0
  this could cause some incompatibility between different logger tools

  for Logger, DEBUG/0 < INFO/1 < WARN/2 < ERROR/3 < FATAL/4,
  for Log4r,  ALL/0 < DETAIL/1 < DEBUG/2 < INFO/3 < WARN/4 < ERROR/5 < FATAL/6.

  anyway, it is not in good pattern.

* suggestion
  logger.debug { ... }
  if current level is greater than DEBUG, the block will not be
  evaluated. it is also efficient.

  following is also supported by most loggers.
  logger.info { ... }
  logger.warn { ... }
  logger.error { ... }
  ...
2012-04-27 15:26:49 +08:00
..
conversions.rb RUBY-226 minor: license update 2011-01-17 12:26:32 -05:00
core_ext.rb RUBY-364 2011-11-16 13:40:55 -05:00
logging.rb fix log debug level detect 2012-04-27 15:26:49 +08:00
node.rb minor: refactor TCP_NODELAY 2012-04-08 10:48:25 -04:00
pool_manager.rb RUBY-416 threading with refresh test fixes 2012-03-05 14:40:05 -05:00
pool.rb minor: refactor TCP_NODELAY 2012-04-08 10:48:25 -04:00
server_version.rb RUBY-226 minor: license update 2011-01-17 12:26:32 -05:00
ssl_socket.rb minor: refactor TCP_NODELAY 2012-04-08 10:48:25 -04:00
support.rb RUBY-406 added ReplSetConnection read preference :secondary_only 2012-02-16 12:59:52 -05:00
tcp_socket.rb minor: refactor TCP_NODELAY 2012-04-08 10:48:25 -04:00
uri_parser.rb minor: testing fixes, cleaning output 2012-04-04 16:44:01 -04:00