[Question/Improvements] Log HttpListenerException in HttpServer.cs ConnectionThreadStart method

[Ryujose]

Hi guys.

I found this exception without any logging, it only have a print for a console env. I think that it could be useful to log this point to let the end-user know what exactly is happening.

[gbirchmeier]

I'm realizing that QF/n's current logging interface might be too limited.

It's obvious to me that this should be loggable, but the normal QF/n log interface ties each log to a Session, and HttpServer does not apply to any session. So how should this HttpServer log be configured? It doesn't seem wise to just hack something out right now. I'm going to think about it for a little while (and hopefully come back to this before another year has passed).

[gbirchmeier]

On the upside, I just rewrote the whole dang HttpServer (#829), and it now handles exeptions much better, so ideally there won't be any unexpected shutdowns to need to log.

[gbirchmeier]

I wrote a fix that added an ILogFactory to the HttpServer constructor, but that's bad, because it means there will be two NonSessionLogs pointing to the same log file. If they try to log at the same time, then both NSLs will be contending over the same resource (the file).

I'm going to put put this one on hold until the #899 log redesign matures. I think a proper design will emerge from that.