Project

General

Profile

Bug #84

Handle network disconnects

Added by Sputnick about 16 years ago. Updated over 15 years ago.

Status:
Closed
Priority:
High
Assignee:
Sputnick
Category:
Quassel Core
Target version:
0.2.0-alpha1
Start date:
Due date:
% Done:

0%

Estimated time:
Version:
0.13.1
OS:
Any

Description

Network disconnects need to be recognized (ping/pong) and taken care of by an automatic reconnect (plus channel rejoin) if possible. With the new core arch, we should be able to put everything in NetworkConnection (which must store which channels to rejoin though).

NetworkConnections should only go away on explicit disconnect (/quit), and stay alive otherwise.

History

#1 Updated by EgS about 16 years ago

I think QUITs only don't suffice.
If the Server explicitly tells you to go away, then it doesn't make sense to endless loop in a reconnecting process.

I don't know from my head how G-Lining, K-Lining and Stuff are propagated to the Client, but at least a KILL is quite verbose ;)

Also available in: Atom PDF