Ivan Kozlovic 947798231b [UPDATED] TCP Write and SlowConsumer handling ...

- All writes will now be done by the writeLoop, unless when the
  writeLoop has not been started yet (likely in connection init).
- Slow consumers for non CLIENT connections will be reported but
  not failed. The idea is that routes, gateway, etc.. connections
  should stay connected as much as possible. However if a flush
  operation times out and no data at all has been written, the
  connection will be closed (regardless of type).
- Slow consumers due to max pending is only for CLIENT connections.
  This allows sending of SUBs through routes, etc.. to not have
  to be chunked.
- The backpressure to CLIENT connections is increased (up to 1sec)
  based on the sub's connection pending bytes level.
- Connection is flushed on close from the writeLoop as to not block
  the "fast path".

Some tests have been fixed and adapted since now closeConnection()
is not flushing/closing/removing connection in place.

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>

2019-12-31 15:06:27 -07:00

..

log_test.go

[ADDED] LogSizeLimit option

2019-11-21 15:26:33 -07:00

log.go

[ADDED] LogSizeLimit option

2019-11-21 15:26:33 -07:00

syslog_test.go

[UPDATED] TCP Write and SlowConsumer handling

2019-12-31 15:06:27 -07:00

syslog_windows_test.go

Tune some code/test for Windows

2019-11-21 14:32:46 -07:00

syslog_windows.go

Add Warnf to logger interface

2018-09-10 14:50:48 -07:00

syslog.go

Update for client rename

2019-05-10 15:11:30 -07:00