The logging library currentkly throws an exception if the server is not available when the library is first constucted or if the socket is closed later on. I think it should:
- attempt to connect in the background (and not block in the constrcutor)
- silenlt handle a socket close/disconnect
- silently discard any log events generated when there is no socket connection
- automatically and continually attempt to reconnect silently in the background
What do you think?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The logging library currentkly throws an exception if the server is not available when the library is first constucted or if the socket is closed later on. I think it should:
- attempt to connect in the background (and not block in the constrcutor)
- silenlt handle a socket close/disconnect
- silently discard any log events generated when there is no socket connection
- automatically and continually attempt to reconnect silently in the background
What do you think?
agreed
sounds like a plan to me
done in rev 16
Hooray!