Buffer support in log4net-loggly library during network outage

[Shwetajain148]

• Store logs during network outage.
• Rotate stored logs while running out of memory.
• Send buffered logs after re-connection.
• Handle bad token error.
• Truncate event over 1 MB size.
• Make buffer option configurable.
• Refactor: Fix linting issue(Library follow mixed spacing tab and 4 spaces)
• Testing

[mchaudhary]

Will this generate Null exception ?

[mchaudhary]

This function name is pretty funky setValidInvalidFlag. I think what we are doing is if we getting Forbidden error we are marking token as invalid so we should call this function setTokenValid(false).

[mchaudhary]

This logic of else if (totalRetries == 1) is also very confusing since this has no relation with above if (response != null). We should always have if and else if in conjunction. I understand what you are trying to do here. You are basically saying if there is exception and the it is not first time lets put it in buffer. I think we can make code such that it is more easy to understand.

[Shwetajain148]

@mchaudhary:
In case of network outage, response variable will be null because request to the remote server couldn't be completed.

When response is null, I am just storing logs into buffer otherwise checking for bad token error(403). Other than bad token status, we are storing logs into the buffer.

Please Review.