[kopete-bugs] [Bug 198789] Kopete disconnects after several xmpp ping messages from jabber server

Roman Jarosz kedgedev at gmail.com
Tue Apr 27 21:27:41 CEST 2010


https://bugs.kde.org/show_bug.cgi?id=198789





--- Comment #65 from Roman Jarosz <kedgedev gmail com>  2010-04-27 21:27:33 ---
Just to clear things, most protocols have they own ping packet so they can
detect when the connection is broken because otherwise the detection would only
occur when we (Kopete/protocol) send something. So if I simplify it without the
ping packets and without user interaction the connection could be broken for
hours and Kopete will not detect it.

The SocketTimeoutWatcher does this, when Kopete(protocol) sends something to
server it check if the server got the packet, to be precise if we got the TCP
acknowledge packet within 15 seconds, if not it closes the socket and Kopete
reconnects the protocol.

SocketTimeoutWatcher is there for all protocols because on linux (maybe on
other platforms too) when kernel doesn't get ACK packet it disconnects the
connection after long time something like 10 or more minutes so with
SocketTimeoutWatcher we can detect it within seconds.

I thing that we may mix to bugs here:
1. Unstable Internet connection => SocketTimeoutWatcher disconnects often.
2. Jabber protocol problem with ping.

Btw. I use jabber.cz and ICQ and I don't have any problems.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the kopete-bugs mailing list