Local history storage #4

New Issue

blue · 2019-04-18T20:32:59Z

blue commented

2019-04-18 20:32:59 +00:00

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

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

Seems like it's done

blue closed this issue

2019-05-15 17:38:45 +00:00

Sign in to join this conversation.