Project

General

Profile

Bug #500

Detection of forced disconnects takes very long (Freenode)

Added by amiconn almost 10 years ago. Updated almost 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Quassel Core
Target version:
Start date:
01/25/2009
Due date:
02/16/2009
% Done:

100%

Estimated time:
1.00 h
Version:
0.3.1+
OS:
Any

Description

Whenever the internet connection is dropped by force (my ISP does this once per day), the core needs quite long to detect this disconnect (15..20 minutes on Freenode). During the timeout period I can still write into any buffer; the text just goes nowhere, without any indication that it didn't reach the server.

As discussed in #quassel, the solution is probably to make the core ping the server periodically, if no message(s) arrive from the server within a certain interval. Monitoring the network activity of another IRC client has shown that it uses this method to quickly detect disconnects even on Freenode, using a ping interval of approx. 30 seconds.

Associated revisions

Revision 32c550d8 (diff)
Added by Marcus Eggenberger almost 10 years ago

fixes #500 - improved detection of disconnects from irc

History

#1 Updated by EgS almost 10 years ago

  • Status changed from New to Confirmed
  • Estimated time set to 1.00 h

Quassel already pings the IRC server periodically to determine the lag to the IRC network. (this is currently only visible in the tooltip of the network item). Should be fairly easy to hook in there and disconnect after a given timeout.

#2 Updated by EgS almost 10 years ago

  • Due date set to 02/16/2009
  • Status changed from Confirmed to Assigned
  • Assignee set to EgS
  • Target version set to 0.4.0
  • OS set to Any

#3 Updated by EgS almost 10 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF