Project

General

Profile

Bug #397

Outgoing messages are not necessarily sent but no indication is given

Added by Anonymous about 7 years ago. Updated almost 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
01/26/2012
Due date:
% Done:

0%

Estimated time:
Affected version:
hg
Locale:
Close

Description

The following scenario: I type an outgoing message. After pressing send but before it is transmitted to the server my connection fails for whatever reason. I however assume it's been sent since I can't see any indication in the chatlog that it is not. This is less likely with trunk as beem might close due to the connection loss but very likely with the account branch, I guess.

Hence I'd like to suggest to show an indication (yellow warning sign, spinner, the word "pending") that disappears after the server confirmed receiving the message/after it was transmitted successfully. Beem should retry to transmit the message until it was successful or until the session is terminated. If chat logs are written out the successful transmission should be stored in the log. If beem starts and reads a log file and finds an unsent message it needs to retransmit it and store it as transmitted in the end. Alternatively it could show "not sent" or a red cross icon to indicate that it wont try again.

I set the priority to high as reliability is one of the most important key features of a messenger client. If I can't be sure that something I typed (and which appears in the chatlog) is sent to (at least) the server I can not use that messenger client for a reliable conversation.


Related issues

Related to Feature #400: Implement XEP-0198 Stream ManagmentNew2012-01-26

History

#1 Updated by Frédéric Barthéléry almost 7 years ago

  • Priority changed from High to Normal

Also available in: Atom PDF