Pending messages to error on disconnect #48
Labels
No Label
Bug
Documentation
Easy
Feature
Localization
Packaging
Refactoring
Test
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blue/squawk#48
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Now I have all messages saved in the database even if they are not yet sent.
It would be nice to have a way to make those pending messages marked as error messages if they are pending on disconnect, for the user was able to resend them
Additionally - I could think of making some list on hdd, that lists all the messages that was pending on disconnect, and try to resend them automatically when the connection is back, or on the next startup