Added VPP state 'NotResponding' 66/27966/1
authorVladimir Lavor <vlavor@cisco.com>
Fri, 17 Jul 2020 12:00:11 +0000 (14:00 +0200)
committerVladimir Lavor <vlavor@cisco.com>
Fri, 17 Jul 2020 12:00:11 +0000 (14:00 +0200)
commita155cd438c6558da266c1c5931361ea088b35653
treee3575e1d925f7c0859857677fa760ee9e935a51d
parentd1f24d37bd447b64e402298bb8eb2479681facf9
Added VPP state 'NotResponding'

This change allows informing client about the current
VPP state in more detail.

* In case the VPP is overloaded but keeps its configuration,
  client received 'NotResponding' event message
* If the VPP process dies (the socket is closed), the client
  receives 'Disconnected' event message

Additional fix: event messages are discarded if the buffer is
full. This could cause GoVPP to hang after some time in case
the client was not receiveing events.

Change-Id: I94a4647f6643f1d97bf52e5d7996d70229b0577d
Signed-off-by: Vladimir Lavor <vlavor@cisco.com>
core/connection.go