We are making logging unnecessarily complex for ourselves by passing a special logger object around everywhere. Since this object is just a wrapper around Python's own logging module, we might as well use that directly.
That way every component of ThinLinc can easily handle logging without having to worry about how to propagate the logging object the correct way all the way from the initial python file.
The only thing that is in tllogger that is ThinLinc specific is reading settings from hiveconf and configuring the main logging object with destination and format. So that would probably need to be kept around. But everything else can be purged.