blue/squawk
blue/squawk
2
3
Fork 8
Code Issues 23 Pull Requests 3 Actions Releases 10 Wiki Activity

Local history storage #4

New Issue
Closed
opened 2019-04-18 20:32:59 +00:00 by blue · 2 comments
blue commented 2019-04-18 20:32:59 +00:00
Owner
Copy Link

https://xmpp.org/extensions/xep-0313.html gives terrible history management, I need to keep the history locally and may be request as user needs.

https://xmpp.org/extensions/xep-0313.html gives terrible history management, I need to keep the history locally and may be request as user needs.
blue added this to the 0.1.0 milestone 2019-04-18 20:32:59 +00:00
blue self-assigned this 2019-04-18 20:32:59 +00:00
blue added the
Feature
 label 2019-04-18 20:32:59 +00:00
blue commented 2019-04-20 20:18:25 +00:00
Author
Owner
Copy Link

Not sure yet how exactly to organize that. How 'bout that:

  • Client requests history if it's open for the first time or if user scrolls to the top and there is an info that there is some more history
  • Account model requests that history from Contact model, contact model either gives it right away either emits the signal, that it needs more history.
  • Account model gets the signal and requests the history from MAM, feeds it back to the client model and flushes in the end to make it on the same database transaction.
  • Contact model concludes when it's enough and triggers the response event or the even about the state that there is no more history available
Not sure yet how exactly to organize that. How 'bout that: - Client requests history if it's open for the first time or if user scrolls to the top and there is an info that there is some more history - Account model requests that history from Contact model, contact model either gives it right away either emits the signal, that it needs more history. - Account model gets the signal and requests the history from MAM, feeds it back to the client model and flushes in the end to make it on the same database transaction. - Contact model concludes when it's enough and triggers the response event or the even about the state that there is no more history available
blue commented 2019-05-15 17:38:31 +00:00
Author
Owner
Copy Link

Seems like it's done

Seems like it's done
blue closed this issue 2019-05-15 17:38:45 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Bug
Something is not working
Documentation
Documentation related issues
Easy
Feature
New feature
Localization
Localization related issues
Packaging
Issues related to packaging and building
Refactoring
Need to reimplement something in a better way
Test
Need to test something
No Label
Feature
Milestone
No items
No Milestone 0.1.0
Assignees
Clear assignees
No Assignees blue
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: blue/squawk#4
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?