Logging needs to be cleaned up

[belisoful]

No one has really touched the Logger code since the start. As part of the forking, I have a utility for grabbing the log from the child fork and bringing it back into the parent. This requires a mergeLog function.

So I started looking at the whole Logger and comparing it to Yii.

While updating the logger, it needs profiling and a log flusher for long running processes.

[belisoful]

I'm reviewing the logger.... because. The TProcessHelper has an Application behavior for merging child process logs back into the main thread. mergeLogs is needed but the Logging needs so much more.

Interesting things...

• TLogger needs an onFlushLogs event for the TLogRouters to patch into, rather than the TLogRouter patching into onEndRequest. ++.
• TLogger needs to trigger onFlushLogs when onEndRequest is raised. (this should patch into the fxTerminate global event in the coming TProcessHelper). ++
• TLogger needs a flush feature when the logs get too big. +
• TLogger needs a mergeLogs ++
• TLogger should log the PID for merging children logs (a feature of the new TProcessHelper) ++
• TLogger needs profiling (begin and end). +
• TLogRoute::Enabled property +
• a Context log message with specified global variables, and context exclusions? Security issues here. +. This will wait for another time.
• prefix for formatting log messages (filled with IP, logged in user ID, sessionID) +