forked from mystiq/hydrogen-web
more notes
This commit is contained in:
parent
64f126ba68
commit
c5bdc8ba05
2 changed files with 6 additions and 0 deletions
|
@ -6,3 +6,7 @@ SyncWriter will need to resolve the related remote id to a [fragmentId, eventInd
|
||||||
The timeline can take incoming events from both the SendQueue and SyncWriter, and see if their related to fragmentId/eventIndex is in view, and then update it?
|
The timeline can take incoming events from both the SendQueue and SyncWriter, and see if their related to fragmentId/eventIndex is in view, and then update it?
|
||||||
|
|
||||||
alternatively, SyncWriter/SendQueue could have a section with updatedEntries apart from newEntries?
|
alternatively, SyncWriter/SendQueue could have a section with updatedEntries apart from newEntries?
|
||||||
|
|
||||||
|
SendQueue will need to pass the non-sent state (redactions & relations) about an event that has it's remote echo received to the SyncWriter so it doesn't flash while redactions and relations for it still have to be synced.
|
||||||
|
|
||||||
|
Also, related ids should be processed recursively. If event 3 is a redaction of event 2, a reaction to event 1, all 3 entries should be considered as updated.
|
||||||
|
|
|
@ -196,3 +196,5 @@ PendingEventStore
|
||||||
get()
|
get()
|
||||||
update()
|
update()
|
||||||
remove()
|
remove()
|
||||||
|
|
||||||
|
make sure to handle race between /sync and /send (e.g. /sync with sent event may come in before /send returns)
|
||||||
|
|
Loading…
Reference in a new issue