Description
When loosing the network connection (e.g. unplug network) while being connected to an XMPP server, it takes around 30 seconds for the local internal connection status to be updated.
During this time, it is still possible to start a session initiation (which in the end fails).
Reproduction
Expected Behaviour
The local connection state should be reliably identified. Actions that require a network connection can't be choosen to perform.
What is the point of adding such an bug entry ? Almost all non critical software applications will fail such badly if you unplug the network device during normal operation.
See "expected behavior".
There is already a Ping implementation in Smack, but guess what. Most servers are not supporting them. Why ? Because you are flooding the server with messages.
There is really NO way to detect network errors of such states in a timely manner.
And really ? Beside WIFI, who unplugs his/her network cable ?
"Private" means "only logged in user may read this ticket"
As nobody will ever implement the "Expected Behaviour" and this scenario is not common, to be more specific unrealistic -> who cares.