Lagerize everything

[ghost]

I'm working on polling servers for BEP5 at the moment and as I go along I add some code for logging the progress and stats of polls. This is useful to see while developing but not so much for a user to see while using the program.

It would be nice to be able to route all logging calls through a configurable logging module that is aware of which types of messages etorrent emits, in the same spirit as accesses to the application config is routed through etorrent_config in my config-module branch.

It wouldn't make any sense to export a function for each message type, just a simple interface in the lines of the following code would do:

 etorrent_log:info(dht_poll, "blalala ~w", [Term])

[jlouis]

Makes sense. Consider routing anything in log.hrl through it as well.

[jlouis]

This is still ongoing, but we should definitely be using lager all over the place rather than roll our own logging framework inside etorrent.