Context on lastdisconnect replication

Bug #402441 reported by Jeremy Nickurak on 2007-07-30
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

As it is, lastdisconnect replays text immediately following the disconnect, but nothing before. This replayed text can be difficult to recognize as part of a conversation without the previous lines. Ideally a small portion (10-15 lines, or 5-10 minutes?) of the text leading up to the disconnect should be included as well, to give the replayed text context, and provide continuity between sessions. It's also easy in the event of a client crash to miss messages that occur after a UI failure, but before the disconnect.

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

delaying to 3.1

Jelmer Vernooij (jelmer) on 2009-07-24
Changed in ctrlproxy:
status: In Progress → Triaged
Jelmer Vernooij (jelmer) on 2010-09-09
Changed in ctrlproxy:
assignee: Jelmer Vernooij (jelmer) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers